Companion robot for personal interaction

ABSTRACT

A mobile robot guest for interacting with a human resident performs a room-traversing search procedure prior to interacting with the resident, and may verbally query whether the resident being sought is present. Upon finding the resident, the mobile robot may facilitate a teleconferencing session with a remote third party, or interact with the resident in a number of ways. For example, the robot may carry on a dialogue with the resident, reinforce compliance with medication or other schedules, etc. In addition, the robot incorporates safety features for preventing collisions with the resident; and the robot may audibly announce and/or visibly indicate its presence in order to avoid becoming a dangerous obstacle. Furthermore, the mobile robot behaves in accordance with an integral privacy policy, such that any sensor recording or transmission must be approved by the resident.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of, and incorporates by referenceherein in its entirety, U.S. patent application Ser. No. 13/487,447,filed Jun. 4, 2012, now abandoned, which is a continuation of, andincorporates by reference herein in its entirety, U.S. patentapplication Ser. No. 12/842,314, filed Jul. 23, 2010, now U.S. Pat. No.8,195,333, which is a continuation of, and incorporates by referenceherein in its entirety, U.S. patent application Ser. No. 12/199,653,filed Aug. 27, 2008, now U.S. Pat. No. 7,957,837, which is acontinuation of, and incorporates by reference herein in its entirety,U.S. patent application Ser. No. 11/541,386, filed Sep. 29, 2006, nowU.S. Pat. No. 7,720,572. This application claims priority to andincorporates by reference herein in their entireties, the following:U.S. Provisional Patent Application Ser. No. 60/746,491, filed May 4,2006; U.S. Provisional Patent Application Ser. No. 60/745,006, filedApr. 17, 2006; U.S. Provisional Patent Application Ser. No. 60/722,935,filed Sep. 30, 2005. Additionally, this application incorporates byreference herein in their entireties U.S. patent application Ser. No.11/541,422, filed Sep. 29, 2006, and U.S. patent application Ser. No.11/541,479, filed Sep. 29, 2006.

FIELD OF THE INVENTION

The present invention relates generally to autonomous mobile robots forinteracting with people and, more specifically, to autonomous mobilerobots for assisting persons with various tasks.

BACKGROUND OF THE INVENTION

Robotic research platforms have been developed for interacting withpeople in home situations, such as the elderly, children, or others whomay benefit from an interactive robot assistant. These robotic platformsoften do not consider the actual home environment, or personalpreferences and concerns, such as making a companion robot non-intrusiveand a welcome guest in the home environment.

Certain platforms have been developed which assist caregivers incarrying medications, providing amusing interaction, and/or providingteleconferencing tools, many remain research platforms: they tend to beso large, heavy, and unwieldy, as to be inappropriate for use in anordinary home. These robotic platforms are generally tested ininstitutions, where some surveillance is expected and privacy andpersonal dignity tend already to be adversely affected, and may not besuitable for use in private homes, where expectations for privacyprotection are higher.

Simply making a robot smaller, however, does not correct theseshortcomings. Though a robot may be sufficiently small to be carried,the contemplated use is typically in a single room, with limited abilityto be useful throughout an entire home. Low-weight platforms tend alsoto be low to the ground, and generally out of view of residents who maybe moving about in the same rooms, creating a danger for those withbalance or mobility issues. In short, previous robots suffer fromlimited usability, and thus do not function as a welcoming and versatileassistant to a human.

SUMMARY OF THE INVENTION

In one aspect, the invention relates to a robot for regimen compliancemanagement, including a processor, a memory accessible by the processor,a sensor capable of detecting a presence of a person within a detectionrange of the robot, a communication interface capable of generating ahuman-perceptible signal, a drive operatively connected to the processorthat moves the robot, a scheduler routine executable on the processorthat checks at least one of a medication dosage information for amedication event and a health-related information for a regimen event,and in advance of the event, initiates a person finding routine, aperson finding routine executable on the processor that instructs thedrive to move the robot about an environment and to stop in a positionproximate a person, and a regimen compliance manager for ensuringcompliance of a person with a regimen routine.

In one aspect, the invention relates to a robot for regimen compliancemanagement, including a processor, a memory accessible by the processorthat includes personal medication dosage information, a sensor capableof detecting the presence of a person within a detection range of therobot, a communication interface capable of generating ahuman-perceptible signal and receiving a compliance or non-complianceindication from the person, a drive operatively connected to theprocessor that moves the robot, a scheduler routine executable on theprocessor that checks the personal medication do sage information formedication events, and in advance of a medication event, initiates aperson finding routine, a person finding routine executable on theprocessor that instructs the drive to move the robot about the householdchecking the sensor suite for the presence of the person and to stop ina position next to the person, a matching routine executable on theprocessor that sends a human perceptible signal to the person includinginformation regarding the location of medication to be taken and guidesthe person to the medication. In certain embodiments of the aboveaspect, the communication interface is receiving a compliance ornon-compliance indication from the person and the memory accessible bythe processor includes postponement rules, and further including aregimen compliance snooze routine that upon recognition of anon-compliance indication from the person, checks the personalmedication dosage information and sets a new medication event compatiblewith the postponement rules.

In another aspect, the invention relates to a robot for regimencompliance management, including a processor, a memory accessible by theprocessor that includes personal medication dosage information, thememory including postponement rules defining permissible conditions forpostponing dosage, a sensor capable of detecting the presence of aperson within a detection range of the robot, a communication interfacecapable of generating a human-perceptible signal and receiving acompliance or non-compliance indication from the person, a driveoperatively connected to the processor that moves the robot, a schedulerroutine executable on the processor that checks the personal medicationdosage information for medication events, and in advance of a medicationevent, initiates a person finding routine, a person finding routineexecutable on the processor that instructs the drive to move the robotabout the household and to stop in a position next to the person, amatching routine executable on the processor that sends a humanperceptible signal to the person including information regardingmedication to be taken, and a regimen compliance snooze routine thatupon recognition of a non-compliance indication from the person, checksthe personal medication dosage information and sets a new medicationevent if postponing medication is compatible with the postponementrules.

In yet another aspect, the invention relates to a robot for regimencompliance management, including a medication cache that receives loadedmedication to be carried by the robot, a processor, a memory accessibleby the processor that includes personal medication dosage informationand postponing rules, a sensor capable of detecting the presence of aperson within a detection range of the robot, a communication interfacecapable of generating a human-perceptible signal, a drive operativelyconnected to the processor that moves the robot, a scheduler routineexecutable on the processor that checks the personal medication dosageinformation for medication events, and in advance of a medication event,initiates a person finding routine, a person finding routine executableon the processor that instructs the drive to move the robot about thehousehold checking the sensor suite for the presence of the person andto stop in a position next to the person, a matching routine executableon the processor that sends a human perceptible signal to the personincluding information regarding the medication carried in the medicationcache. In certain embodiments of the above aspect, the robot includes amedication loading routine executable on the processor that sends ahuman perceptible signal to the person including information regardingloading the medication cache for later administration and informationguiding the person to the medication.

In still another aspect, the invention relates to a robot system forregimen compliance management, having a medication cache that receivesloaded medication, a processor, a memory accessible by the processorthat includes personal medication dosage information and postponingrules, a sensor capable of detecting the presence of a person within adetection range of the robot, a communication interface capable ofgenerating a human-perceptible signal, a drive operatively connected tothe processor that moves the robot, a scheduler routine executable onthe processor that checks the personal medication dosage information formedication events, and in advance of a medication event, initiates aperson finding routine, a person finding routine executable on theprocessor that instructs the drive to move the robot about the householdchecking the sensor suite for the presence of the person and to stop ina position next to the person, and a medication loading routineexecutable on the processor that sends a human perceptible signal to theperson including information regarding loading the medication cache forlater administration, and information guiding the person to themedication cache.

In another aspect, the invention relates to a robot for regimencompliance management, including a network interface that connects therobot to a remote location at which a caregiver may connect to therobot, a processor, a memory accessible by the processor that includespersonal medication dosage information, a sensor capable of detectingthe presence of a person within a detection range of the robot, acommunication interface capable of generating a human-perceptible signaland receiving a compliance or non-compliance indication from the person,a drive operatively connected to the processor that moves the robot, ascheduler routine executable on the processor that checks the personalmedication dosage information for medication events, and in advance of amedication event, initiates a person finding routine, a person findingroutine executable on the processor that instructs the drive to move therobot about the household checking the sensor suite for the presence ofthe person and to stop in a position next to the person, a regimencompliance reminder routine executable on the processor that, uponrecognition of a non-compliance indication from the person, contacts thecaregiver via the network interface. In certain embodiments of the aboveaspect, the robot includes an inbound communication channel for thecaregiver to send a human-perceptible signal through the inboundcommunication channel and via the communication interface.

In yet another aspect, the invention relates to a robot for regimencompliance management, including a network interface that connects therobot to a remote location at which a caregiver may connect to therobot, a processor, a memory accessible by the processor that includeshealth-related regimen information, a sensor capable of detecting thepresence of a person within a detection range of the robot, acommunication interface capable of generating a human-perceptiblesignal, an inbound communication channel for the caregiver to send ahuman-perceptible signal through the inbound communication channel andvia the communication interface, a drive operatively connected to theprocessor that moves the robot, a scheduler routine executable on theprocessor that checks the health-related regimen information for regimenevents, and in advance of a health-related regimen event, initiates aperson finding routine, a person finding routine executable on theprocessor that instructs the drive to move the robot about the householdchecking the sensor suite for the presence of the person and to stop ina position next to the person, and a regimen compliance guide accessroutine executable on the processor that connects a communicationsession with a caregiver via the network interface.

In another aspect, the invention relates to a method of human-robotinteraction, including receiving a communication script segment,outputting to a person at least one of a visible component of thecommunication script segment and an audible component of thecommunication script segment, and controlling at least one of a robotexpression component accompanying the output component and a robotresponse to an input by a person.

In still another aspect, the invention relates to a method ofhuman-robot interaction, including receiving a communication scriptsegment, including an output query sub-script text and a response treeof five or less sub-script response text candidate, associating theoutput query text with an audible output signal, and outputting theaudible output signal as a spoken query to a person, displaying theoutput query sub-script text together with the five or less sub-scriptresponse text candidates on a display of the robot, receiving an audioinput signal recording a person's response to the audible output signal,processing the audio input signal to recognize if the audio input signalincludes speech corresponding to any one of the five or less displayedsub-script response text candidates, if the audio input signal is notrecognized to include speech corresponding to any one of the four orless sub-script response text candidates, issuing an output signal toprompt the user to retry communicating a response to the audible outputsignal, and if the audio input signal is recognized to include speechcorresponding to any one of the five or less sub-script response textcandidates, issuing an output signal including a repetition of the oneof the five or less sub-script response text candidates that wasrecognized. Embodiments of the above aspect include, after theconfirmation signal is issued monitoring for a confirmation of thecorrectness or incorrectness of the one of the four or less sub-scriptresponse text candidates that was recognized. In still other embodimentsissuing an output signal to prompt the user to retry communicating aresponse to the audio output signal includes, highlighting the displayedsub-script text on a display of the robot, and receiving an input signalselecting any one of the five or less displayed sub-script response textcandidates via a manually operated control associated with the display.In additional embodiments two of the five or less sub-scripts responsetext candidates are a simple affirmative and simple negative response,and further include processing the audio input signal to recognize ifthe audio input signal includes speech corresponding to a family ofaffirmative responses equivalent to the simple affirmative response orincludes speech corresponding to a family of affirmative responsesequivalent to the simple negative response. In other embodiments one ofthe five or less sub-scripts response text candidates is a response textcandidate that is common to a majority of communication script segments.In still other embodiments, no two of the five or less sub-scriptsresponse text candidates are a simple affirmative and simple negativeresponse, and further include processing the audio input signal torecognize if the audio input signal includes speech corresponding to afamily of affirmative responses equivalent to the simple affirmativeresponse or includes speech corresponding to a family of affirmativeresponses equivalent to the simple negative response. In otherembodiments of the robot, the response tree is a response tree of threeor less sub-script response text candidates, and none of the responsetext candidates is simple affirmative response or simple negativeresponse. Other embodiments include converting the response tree textsubscript into a set of menu choices displayed on the display.

In another aspect, the invention relates to a method of human-robotinteraction, including receiving a communication script segment,including an output query sub-script text and a response tree of five orless sub-script response text candidate, associating the output querytext with an audible output signal, and outputting the audible outputsignal as a spoken query to a person, displaying the output querysub-script text together with the five or less sub-script response textcandidates on a display of the robot, receiving an audio input signalrecording a person's response to the audible output signal, processingthe audio input signal to recognize if the audio input signal includesspeech corresponding to any one of the five or less displayed sub-scriptresponse text candidates, if the audio input signal is recognized toinclude speech corresponding to any one of the five or less sub-scriptresponse text candidates, issuing an output signal including arepetition of the one of the five or less sub-script response textcandidates that was recognized if the audio input signal is notrecognized to include speech corresponding to any one of the four orless sub-script response text candidates, highlighting the displayedsub-script text on a display of the robot, then receiving an inputsignal selecting any one of the five or less displayed sub-scriptresponse text candidates via a manually operated control associated withthe display.

In yet another aspect, the invention relates to a method of human-robotinteraction, including asynchronously executing a plurality of motionbehaviors, including motion behaviors responsive to events, receiving acommunication script segment, including dialogue branches with robotspeech prompt text and human response text, interpreting thecommunication script segment to generate an audible robot speech prompt,receiving input from a person as a response to the audible robot speechprompt, interrupting a dialogue branch in response to an event detectedby one of the plurality of behaviors to execute an asynchronousresponse, and recovering the dialogue branch after the execution of theasynchronous response.

In still another aspect, the invention relates to a method ofhuman-robot interaction, including receiving a communication scriptsegment, including dialogue branches with robot speech prompt text andhuman response text, associating the output query text with an audibleoutput signal, and outputting the audible output signal as a spokenquery to a person, modulating the dialogue branch to show a desiredexpression during the communication script segment by adding at leastexpression motion selected from a head movement sequence including nodaxis head movement or turn axis head movement, or a robot movementsequence including movement of the entire robot.

In another aspect, the invention relates to a method of human-robotinteraction, including receiving a communication script segment,including dialogue branches with robot speech prompt text, humanresponse text, and robot expression motion tags, interpreting thecommunication script segment to generate an audible robot speech promptand robot expression motions according to the dialogue branches,receiving input from a person as a response to the audible robot speechprompt, interrupting an expression motion in response to an eventdetected by the robot to execute a corrective behavior to reposition therobot according to the event, and recovering the dialogue branch afterthe execution of the corrective behavior.

In another aspect, the invention relates to a method of robotself-navigation for a robot, the method including monitoring at leastone of a sensor and an input, comparing a signal from at least one ofthe sensor and the input to at least two predetermined conditions, andperforming at least one of (a) an action, if the signal corresponds to afirst condition; and (b) a movement of the robot, if the signalcorresponds to a second condition.

In one aspect, the invention relates to a method of robotself-navigation, including monitoring a sensor capable of detecting thepresence of a person within a detection range of the robot, improving apresence score when the person is detected within the detection range ofthe robot, decaying the presence score to progressively worsen, drivingin a direction to move the robot to a different location when thepresence score decays to a first threshold presence score, parking therobot in a location proximate to the person when the presence scoreimproves to a second threshold presence score.

In another aspect, the invention relates to a method of robotself-navigation, including monitoring a sensor capable of detecting thepresence of a detectable object within a detection range of the robot,improving a presence score when a detectable object is detected withinthe detection range of the robot, decaying the presence score toprogressively worsen, driving in a direction to move the robot to adifferent location when the presence score decays to a first thresholdpresence score. In certain embodiments, the sensor suite is capable ofdetecting detectable objects including a person and a charging station,and the method further includes parking the robot in a charging stationlocated proximate to the person, engaged to recharge, when the presencescore improves to a second threshold presence score. In otherembodiments, the driving includes moving the robot to a succession ofdifferent locations until the presence score improves to a secondthreshold presence score.

In yet another aspect, the invention relates to a method of robotself-navigation, including monitoring a sensor suite capable ofdetecting the presence of a detectable object within a detection rangeof the robot, detectable objects including either or both of a personand a charging station, improving a presence score when a detectableobject is detected within the detection range of the robot, decaying thepresence score to progressively worsen, driving in a direction to movethe robot to a different location when the presence score decays to afirst threshold presence score, and parking the robot in a chargingstation located proximate to the different location and to the person,engaged to recharge, when the presence score improves to a secondthreshold presence score.

In another aspect, the invention relates to a mobile robot forinteracting with a person, including a first detector for detecting atleast one of a person and an object within a first predetermined spaceproximate the robot, a second detector for detecting at least one of aperson and an object within a second predetermined space proximate therobot, a physical contact device to detect contact between at least oneof a person and an object, wherein at least one of the first detector,the second detector, and the contact device triggers a safety condition,and a controller configured to immobilize the robot when the safetycondition is detected.

In still another aspect, the invention relates to a method of robotself-navigation, including generating an annunciator activation signalin response to a detected condition, activating an annunciator upon anannunciator activation signal, monitoring a sensor for a detectedresponse from a person, checking whether the detected response includesa sought response, if the checking confirms the detected responseincludes a sought response, activating a found person success routine,and if the checking confirms the detected response includes a soughtresponse, identifying a passage from a present chamber, and driving in adirection to move the robot through the passage from the present chamberto a new chamber.

It is a preferably a function of the robot to act as a confidence,trust, and bonding manager. The robot is crafted to boost user trust andemotional attachment, which is beneficial in itself and provides genericbenefits for any and all other applications, increasing their successrate. This function addresses the challenge of introducing new andunfamiliar technology (especially autonomous, self-controlled, mobiletechnology) into the lives of ordinary persons.

In another aspect, the invention relates to a method for roboticallylocating a person being sought, including monitoring a sensor suite fora non-noise signal indicative of the presence of a person, and if thenon-noise signal corresponds to a sought response, then activating afound person success routine, and if the non-noise signal does notcorrespond to a sought response or if no response is identified, thenselecting one of (i) identifying a doorway from a present chamber, andnavigating the robot through the doorway from the present chamber to anew chamber, or (ii) controlling a mobile robot to activate anannunciator. In certain embodiments of the above-aspect, the annunciatoremits a sound including the name of the person being sought, and themethod further includes checking the sought response to confirm that thesource of the sought response is a person of the name being sought.

In yet another aspect, the invention relates to a method for navigatinga robot, including receiving a first navigation command representativeof a remote user's selection of a room identity marker, recognizing apresent room, driving among rooms of different room identity accordingto the first navigation command until the robot recognizes being withina room having a room identity corresponding to the selected roomidentity marker, receiving a second navigation command representative ofa remote user's selection of one of a floor location within the roomhaving a room identity corresponding to the room identity marker or alandmark item within the room having a room identity corresponding tothe room identity marker, driving within the room corresponding to theroom identity according to the second navigation command until the robotrecognizes being at one of the floor location or next to the landmarkitem, receiving a third navigation command stream representative of aremote user's command including direction and bearing, driving withinthe room and from the floor location according to the received thirdnavigation command stream representative of a remote user's commandincluding direction and bearing.

In still another aspect, the invention relates to a method for handlingnavigation commands for remotely controlling a robot, includingreceiving a selection of room identities corresponding to available roomidentities in a household, driving among rooms of different roomidentity until the robot captures topological adjacency among roomidentities and correlates each room identity of a household with areceived room identity marker, displaying room identity markerscorresponding to available room identities for a household, the roomidentity markers being displayed according to topological adjacency ofcorresponding room identities and being displayed as a part of agraphical depiction of a house.

In another aspect, the invention relates to a method for handlingnavigation commands for remotely controlling a robot, includingreceiving a selection of room identities corresponding to available roomidentities in a household, driving among rooms of different roomidentity until the robot captures topological adjacency among roomidentities and correlates each room identity of a household with areceived room identity marker, displaying room identity markerscorresponding to available room identities for a household, the roomidentity markers being displayed according to topological adjacency ofcorresponding room identities and being displayed as a part of agraphical depiction of a house, receiving a selection of a room identitymarker via a user interface linked to the displaying room identitymarkers as a first navigation command representative of a remote user'sselection of a room identity marker, recognizing a present room, anddriving among rooms of different room identity according to the firstnavigation command until the robot recognizes being within a room havinga room identity corresponding to the selected room identity marker.

In yet another aspect, the invention relates to a mobile robot forinteracting with a person, including an annunciator configured toaudibly indicate the presence of the robot, a visible beacon configuredto optically indicate the presence of the robot, a proximity curtaindetector configured to detect a person within a curtain covering amajority of the height of the robot and thereafter trigger a safetycondition, a physical impact buffer configured to absorb impact of aperson colliding with the robot, detect the person, and trigger thesafety condition, a floor-level proximity ribbon detector configured todetect objects of less than 2 inches in height and trigger the safetycondition, and a controller configured to immobilize the robot when thesafety condition is detected.

In still another aspect, the invention relates to a mobile robot forinteracting with a person, including a zone detector configured todetect an object within a zone in front of the robot covering asubstantial portion of the height of the robot above 10 inches from theground and thereafter trigger a safety condition, a near zone impactbumper configured to absorb an impact of an object colliding with therobot, detect the object, and trigger the safety condition, a near zoneproximity sensor configured to detect an object in front of the robotbetween 2-10 inches from the ground and trigger the safety condition, anear zone low object proximity sensor configured to detect objects infront of the robot of less than 2-4 inches in height and trigger thesafety condition, and a controller configured to immobilize the robotwhen the safety condition is detected. In embodiments of the aboveaspect, each of the proximity curtain detector, the physical impactbuffer, and the floor-level proximity ribbon detector are configured todetect a person at different distances from a center of the robot. Incertain embodiments, the robot further includes a heat radiationdetector or sound detector checked by the controller, that determinesthat an object encountered in the direction of travel is a person whenheat radiation or sound of an object is above a low threshold andoptionally below a high threshold. In other embodiments, the robot isconfigured to slow to less than 10 cm/sec when an object in thedirection of travel is determined to be a person by heat radiation orsound detection.

In another aspect, the invention relates to a robot for interacting witha resident in an environment, including a sensor adapted to monitor aresident when the robot is in an environment and a resident is withinrange of the sensor, a controller to monitor surveillance data from thesensor, a transmission control routine configured to enable transmissionof surveillance data from the sensor to a location outside anenvironment, if a resident grants permission for the transmission, andan override routine configured to enable transmission of surveillancedata from the sensor to a location outside the environment at least inan emergency condition.

In another aspect, the invention relates to a robot for interacting witha resident in the resident's home, including a sensor capable ofmonitoring the resident when the robot is in the resident's home and theresident is within range of the sensor, a controller connected tomonitor surveillance data from the sensor, a transmission controlroutine configured to enable a transmission of surveillance data fromthe sensor outside the resident's home if the resident grants permissionfor the transmission, and an override routine configured to enable atransmission of surveillance data from the sensor outside the resident'shome (i) in an emergency condition detected by the robot or (ii) after an authorized remote caregiver sends to the robot an authorizationpreviously permitted by the resident and an emergency conditionindication, wherein the transmission of surveillance data by the robotoutside the resident's home is otherwise prohibited. In certainembodiments of the above aspect, the robot includes a connector capableof receiving a lock-out member, wherein the transmission control routineenables transmission of surveillance data from the sensor outside theresident's home only when the lock-out member is inserted in theconnector. In other embodiments, the sensor includes a camera, and therobot includes a privacy controller configured to orient the objectivelens of the camera to face the robot's body when a privacy mode isselected. In alternative embodiments, the robot includes a privacymember configured to physically unplug the sensor when a privacy mode isselected.

In yet another aspect, the invention relates to a robot for interactingwith a resident in the resident's home, including a sensor capable ofmonitoring the resident when the robot is in the resident's home and theresident is within range of the sensor, a controller connected tomonitor surveillance data from the sensor, a connector capable ofreceiving a lock-out member, a transmission control routine configuredto enable a transmission of surveillance data from the sensor outsidethe resident's home if the resident grants permission for thetransmission and only when the lock-out member is inserted in theconnector, and an override routine configured to enable a transmissionof surveillance data from the sensor outside the resident's home onlywhen an emergency condition signal is received by the robot.

In another embodiment, the invention relates to a robot capable ofhuman-robot interaction, including a head assembly including a face atleast one camera mounted proximate the face, and a positionable supporthaving a first position and a second position, the mount supporting atleast one of the face and the at least one camera.

In still another aspect, the invention relates to a robot capable ofhuman-robot interaction, including a head assembly including a headhaving a face on one side, at least one camera mounted within the faceto direct an objective lens of the camera in the same direction as theface, a rotatable pivot supporting the head to permit the head to movesuch that the face and the at least one camera are hidden from view andthe camera is thereby prevented from viewing an area around the robot.In embodiments of the above aspect, the face further includes a matrixpanel electronically controllable to show different configurations ofleft and right eyes composed of matrix elements, and the at least onecamera includes a left camera proximate to the left eye composed ofmatrix elements and a right camera proximate to the right cameracomposed of matrix elements.

In another aspect, the invention relates to a robot capable ofhuman-robot interaction, including a head assembly including a headhaving a face on one side, the face comprising a matrix panelelectronically controllable to show different configurations of left andright eyes composed of matrix elements, a left camera proximate to theleft eye and a right camera proximate to the right eye, each of left andright cameras being mounted near the face to direct an objective lens ofthe camera in the same direction as the face, and at least onepositionable mount supporting the left camera and right camera to eachmove to a position disabled from viewing an area around the robot.

In yet another aspect, the invention relates to a robot system,including a base station, and a robot, the base station including awireless transceiver capable of communicating TCP/IP transmissions overa local wireless protocol, a wired Ethernet connector for communicatingTCP/IP transmissions over a local wired Ethernet accessing the Internet,and an access point circuit for transferring TCP/IP transmissionsbetween the local wired Ethernet and local wireless protocol limited toa predetermined IP address locked to the robot, predetermined shelllevel encryption locked to the robot, and predetermined ports to theInternet open only to the robot, the robot including a wirelesstransceiver capable of communicating TCP/IP transmissions over a localwireless protocol and a client circuit for transferring TCP/IPtransmissions over the local wireless protocol. In embodiments of theabove aspect, the wireless access point includes a plurality of antennasand an antenna diversity circuit. In other embodiments, the wirelessaccess point includes a plurality of antennas and an antenna diversitycircuit and encodes wireless transmissions using orthogonal frequencydivision multiplexing.

In accordance with an embodiment of the present invention, a method forrobotically locating a person being sought may include (a) controlling amobile robot to activate an annunciator upon an annunciator activationsignal, (b) monitoring a sensor suite for any non-noise (noise filtered)response to the annunciator within a limited time period after theactivation, (c) comparing any detected non-noise response to a libraryof sought responses; (d) when the non-noise response does not correspondto a sought response or when no response is identified, identifying adoorway from a present chamber; (e) navigating the robot through thedoorway from the present chamber to a new chamber; (f) generating anannunciator activation signal in response to a detected condition, and(g) repeating (a) through (f) until the non-noise response correspondsto a sought response, then (h) activating a found person successroutine.

The identifying the doorway may include analyzing robot odometry andheading during wall following and identifying successiveodometry/heading combinations indicating a wall end and/or doorway hasbeen traversed. Also, the identifying the doorway may include analyzingrobot signal reflection sensing and identifying a heading toward a wallgap. The identifying the doorway may further include analyzing adynamically built map and identifying a heading toward a wall gap;analyzing an archived map and robot position and identifying a headingtoward a wall gap; analyzing a beacon sensor of a door-designatingbeacon and identifying a heading toward a door designated by the doorbeacon; and/or analyzing a ceiling configuration or pattern of indiciaon a ceiling of a present chamber and identifying a heading toward adoor at a position recognized using the indicia or ceilingconfiguration.

The annunciator may emit a sound including the name of the person beingsought, and the comparing any detected non-noise response to the libraryof sought responses/non-noise response indicates that the source of thenon-noise response is a person being sought. The method may furtherinclude selecting the second location based on an arbitrary heading andan arbitrary distance for the mobile robot to travel; adjusting theheading of the mobile robot when an obstacle or hazard is encountered;and proceeding until the mobile robot has traveled the arbitrarydistance. The new chamber may lie in a different room from the presentchamber, and the method may further include navigating the mobile robotfrom the present chamber location to the new chamber based on one ormore of optical room feature recognition, sonar, RFID room tagging, IRdirectional beacon detection, odometry, inertial guidance, deadreckoning, room mapping, and/or compass navigation.

The method may also include using at least one secondary detectionsystem configured to detect the person being sought, in which the atleast one secondary detection system is selected from infrareddetection, radiative heat detection, acoustic detection, RFID tagdetection, tank circuit detection, motion detection, and/or imageanalysis; or, the method may further include generating a map of astructure in which the mobile robot is located, and selecting the newchamber based on the generated map, in which the new chamber is in adifferent room from the present chamber or lies at least a thresholddistance away from the present chamber.

The generating the map may include controlling the mobile robot totraverse the robot's environment and to detect walls and obstacles; andthe map may be transmitted to the mobile robot by a user. The method mayfurther include locating a closed door, and transmitting an audiblesignal through the door; in addition, the transmitting the audiblesignal may include imparting a knocking sound to the closed door.

In accordance with one embodiment, a mobile robot for interacting with aperson may include a speaker for generating audible content based on arobot behavior; a scheduler configured to trigger a robot behavior inaccordance with the schedule; and a morning robot behavior forinteracting with the person soon after the person awakens regarding asecond robot behavior scheduled later in the day. The robot may alsoinclude a pill dispenser for dispensing medication, in which the secondrobot behavior includes dispensing medication to the person, and inwhich the morning robot behavior includes reminding the person about themedication and/or requesting that a person place the medication into thepill dispenser. The robot may further include a transmitter fornotifying a caregiver when the medication is not dispensed according toschedule.

Also, the robot may further include a sensor for detecting the person; alocater which uses the sensor when locating the person, in which therobot attempts to locate a person prior to the scheduled robot behavior.Further, each robot behavior may include using the speaker to remind theperson of a scheduled robot behavior. The second robot behavior mayinclude guiding the person 2 a predetermined location, in which themorning robot behavior includes verbally reminding the person of anactivity associated with the upcoming second robot behavior; and themorning robot behavior may cognitively reinforce the person'srecollection regarding an activity associated with the later secondrobot behavior.

The mobile robot may further include a visual display, in which at leastone of the morning or second robot behaviors include both displaying andspeaking The mobile robot may further include a privacy controller forpreventing transmission to a caregiver unless the person has givenpermission to notify the caregiver. Also, the robot may include areceiver for receiving the command from the caretaker, in which theprivacy controller is overridden when the command is received.

At least one of the robot behaviors may be input by the person or by thecaregiver; and the mobile robot may cease interaction with the personwhen instructed to stop by the person or by the caregiver.

In accordance with another embodiment, the mobile robot for interactingwith a person may include at least one sensor; a privacy controller forpreventing operation of the sensor unless the person grants permissionfor the sensor to operate; and an override unit configured for enablingoperation of the sensor regardless of the privacy controller when theoverride unit receives an override command. Regarding the mobile robot,the sensor may include at least one of a camera, a microphone, aproximity detector, a heat detector, or a tag detector. The mobile robotmay further include a wireless transmitter for transmitting and outputof the sensor, or a recording unit configured to record the output ofthe sensor. The mobile robot may also include a teleconferencing unitfor transmitting and receiving audio and/or video data, in which theteleconferencing unit includes the sensor, and in which the privacycontroller prevents initiation of a teleconferencing session unless theperson grants permission. In addition the mobile robot may furtherinclude a speech recognition unit for detecting spoken input, in whichthe permission to talk with the sensor and the input by the speechrecognition unit. The mobile robot 1 may control or manipulate an objectin the household of the person (for example, turning on a television ata certain time by using an on-board IR transmitter), or point to anobject or location at a certain time of day, as components of robotoperation.

Also, the override unit may include a receiver for wirelessly receivingthe override command from a remote caregiver. The mobile robot mayattempt to locate the person when an incoming teleconferencing requestis received. Also, the privacy controller may be overridden when therobot detects an emergency condition-for example, if a person appears tobe passed out, in danger, sick, or if there's smoke or if a fire alarmhas been triggered, etc. The sensor may be conspicuously positioned whenoperating, and the sensor may become shrouded, covered, or moved so asnot to be seen by the person when the sensor is not operating.Furthermore, the sensor may include a camera, in which the camera isplaced in an inoperable position when permission to operate is notgranted, and in which a lens of the camera faces an opaque surface inthe inoperable position.

The mobile robot may further include a behavior privacy matrix stored ina computer memory and correlating a plurality of robot behaviors to aplurality of permission to scores, in which the privacy controllerpermits a robot behavior when the robot behavior has been permitted, orprevents the robot behavior when the robot behavior has not beenpermitted.

In accordance with yet another embodiment, a robot for interacting witha person may include an annunciator for audibly indicating the presenceof the robot; a beacon for optically indicating the presence of therobot; a sensor for detecting a safety condition; and a controller forimmobilizing the robot when the safety condition is detected. Theannunciator may continuously or periodically emit a characteristic soundwhen the robot is moving. The beacon may shine a strobe light when therobot is moving, as well. Also, the sensor may include a camera, anoptical sensor, an IR sensor, a key detector, a motion detector, acontact switch, a pressure detector, a proximity sensor, a sonar, alaser based obstacle detector, a noise detector, and/or a microphone,inter alia.

The mobile robot may further include a platform mounted to main chassisof the robot by a stalk, in which the platform and the stalk convey animpression of fragility, and in which the platform extends to theperson's waist-level above the main chassis of the robot. The stalk androbot may have an overall shape and/or mass distribution similar to aninverted pendulum. The mobile robot may further include a tipper ringpositioned along the stalk which prevents the person from inadvertentlycolliding with the platform.

The mobile robot may also include a communication unit for sendinginformation regarding the person 2 a remote terminal operable by acaregiver. The communication unit may not send the information if theperson has not given permission, and in addition, it may periodicallytransmit the information according to a predetermined schedule. Also,the communication unit may send the information when the information haschanged. Alternatively, for example, the communication unit may retrieveinstructions via a computer network.

In another aspect, the invention relates to a method of human-robotinteraction between a resident and a mobile robot, the method includingthe steps of providing a robot comprising a facial display and a soundgenerating device, executing a viseme sequence of a communication scriptsegment via the display, executing a phoneme sequence of thecommunication script segment via the sound generating device, whereinthe viseme sequence and the phoneme sequence are executed substantiallysynchronously, and managing the interaction based at least upon anaction of the resident and a flexible response regimen of the robot. Inone embodiment of the above aspect, the managing step includes an affectbehavior for depicting a response of the robot to an event. The affectbehavior may include the steps of providing the display on a movablehead on the robot, and moving the head from a first position to a secondposition upon an occurrence of an event. In the above method, the firstposition may permit viewing by the resident, and the second position isassociated with at least one of a surprise response, a joy response, aconfusion response, a concern response, and a dejection response. Theaffect behavior further may include the step of displaying a caricature.The caricature is selected from a set of caricatures associated with asurprise response, a joy response, a confusion response, a concernresponse, and a dejection response.

In another embodiment of the above aspect, the managing step includes aninterrupt behavior for responding to an asynchronous response by theresident. The interrupt behavior may include the steps of receiving theasynchronous response, interrupting the execution of the viseme sequenceand the execution of the phoneme sequence upon receipt of theasynchronous response, executing an interrupt sequence, and recoveringthe execution of the viseme sequence and the execution of the phonemesequence subsequent to the interrupt sequence. The interrupt behaviormay include delivering an error message. Delivering the error messagemay include the steps of executing an error viseme sequence via thedisplay, and executing an error phoneme sequence via the soundgenerating device, wherein the execution of the error viseme sequenceand the execution of the error phoneme sequence are substantiallysynchronized. The recovering step may include the step of repeating thesteps of executing the viseme sequence and executing the phonemesequence. The asynchronous may not correspond to at least one of apredetermined set of responses. The above method may also include thesteps of comparing a response to the predetermined set of responses, andexecuting a second viseme sequence and a second phoneme sequence, if theresponse corresponds to at least one response of the predetermined setof responses.

In another embodiment of the above aspect, the managing step may includea regimen compliance behavior for providing instruction to the resident.The regimen compliance behavior includes the steps of storing a regimenand a compliance schedule associated with the regimen, providing areminder to the resident at a predetermined event during the complianceschedule, comparing a response from the resident to a set ofpredetermined responses, and performing an action based on the responsefrom the resident. In another embodiment, the performing step includesproviding a medicine to the resident. In another embodiment, theperforming step includes providing a second reminder to the resident.The performing step may include communicating with a device remote fromthe robot.

In another embodiment of the above aspect, the managing step may includea remote communication sequence for communicating between the residentand a third party located remote from the resident. In anotherembodiment, the remote communication sequence includes the steps ofproviding a camera on the robot, and changing a status of the camerafrom a first setting to a second setting upon an occurrence of an event.The first setting may permits viewing the resident, and the secondsetting may include a privacy orientation of the camera. The method mayalso include the step of providing a privacy signal to the resident. Theevent may include a permission denial from the resident. The firstsetting includes an unpowered condition of the camera, and the secondsetting includes a powered condition of the camera, and wherein thecamera is oriented for viewing the resident.

In still another embodiment of the above-aspect, the managing stepincludes a navigation manager for moving the mobile robot in anenvironment. The navigation manager includes a human-seeking sequence,the sequence including the steps of activating an annunciator in a firstof a plurality of locations, monitoring a sensor suite for a non-noiseresponse, comparing the non-noise response to a set of predeterminedresponses, activating a success routine if the non-noise responsecorresponds to at least one response of the set of predeterminedresponses, navigating the robot to a next location, and activating theannunciator. The navigating step includes the step of identifying adoorway, which includes at least one of the group of (a) analyzing robotodometry and heading during a wall following mode and identifyingodometry and heading combinations indicating traversal of at least oneof a wall end and a doorway, (b) analyzing signal reflection andidentifying a heading toward a wall gap, (c) analyzing a dynamicallybuilt map and identifying a heading toward a wall gap, (d) analyzing amap and robot orientation relative to the map and identifying a headingtoward a wall gap, (e) analyzing a beacon and identifying a headingtoward the beacon, and (f) analyzing a pattern of indicia on a ceilingand identifying a heading toward a door at a position recognized byutilizing the pattern. In the method, the annunciator emits a soundincluding a name associated with the resident being sought, and whereinthe set of predetermined responses identifies a source of the non-noiseresponse. The method may also include the steps of selecting the nextlocation based on an arbitrary heading and an arbitrary distance for themobile robot to travel, moving in the direction of the arbitraryheading, adjusting a direction of travel of the mobile robot to avoid anobstacle, returning to the arbitrary heading when the obstacle isavoided, and continuing movement in the direction of the arbitraryheading until the mobile robot has traveled the arbitrary distance.Additionally, the method may further include the step of navigating themobile robot to the next location based on at least one of optical roomfeature recognition, sonar, RFID room tagging, IR directional beacondetection, odometry, inertial guidance, dead reckoning, room mapping,and compass navigation. The method may also include the step of using atleast one detector configured to detect a person, wherein the at leastone detector is selected from the group consisting of an infrareddetector, a radiation detector, and acoustic detector, an RFID detector,a tank circuit detector, a motion detector, and an image detector. Inaddition, the method further includes the steps of generating a map of astructure in which the mobile robot is located, and selecting the nextlocation based on the generated map, wherein the next location islocated at least a threshold distance away from a present location ofthe mobile robot. The generating step includes detecting obstacles orreceiving the map electronically from a resident. The method may alsoinclude the steps of locating a closed door, and transmitting an audiblesignal through the door. The transmitting step includes imparting aknocking sound to the door.

In yet another embodiment of the above aspect, the managing stepincludes a safety manager for controlling contact with a resident. Thesafety manager initiates a safety sequence including the steps ofconfiguring an annunciator to indicate a presence of the robot,configuring a beacon to indicate the presence of the robot, configuringa sensor to detect a safety condition, and configuring a controller toimmobilize the robot when the safety condition is detected. Theannunciator emits a predetermined sound when the robot is moving. Thebeacon comprises a strobe light. The sensor includes at least one of acamera, an optical sensor, an IR sensor, a key detector, a motiondetector, a contact switch, a pressure detector, a proximity sensor, asonar detector, a laser-based obstacle detector, a noise detector, and amicrophone. The above method further includes the step of configuring aphysical shape of the robot to limit contact between the resident and abase of the robot. The above method further includes the step ofconfiguring a communication unit for sending information regarding theresident to a remote terminal. Sending information includes receivingpermission from the resident, which is sent according to a predeterminedschedule, upon an occurrence of a change in information, or is exchangedwith a computer.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, features, and advantages of the presentinvention, as well as the invention itself, will be more fullyunderstood from the following description of various embodiments, whenread together with the accompanying drawings, in which:

FIG. 1A is a schematic perspective view of an autonomous mobile robot inaccordance with one embodiment of the present invention;

FIG. 1B is an outline schematic perspective view of the mobile robot ofFIG. 1A;

FIG. 2A is a schematic perspective view of a mobile robot and functionsthereof in accordance with another embodiment of the present invention;

FIGS. 2B-2F are schematic perspective views of functions for the mobilerobot of FIG. 2A;

FIGS. 3A-3C are schematic front views and perspective views of mobilerobots and medicine dispensers and base stations in accordance withother embodiments of the present invention;

FIG. 4A is a schematic bottom view of a mobile robot in accordance withan embodiment of the present invention;

FIG. 4B is schematic top, side, and front views of a mobile robot inaccordance with another embodiment of the present invention;

FIGS. 5A-5B are schematic perspective views of the mobile robot of FIG.1A;

FIG. 5C is a schematic view of a privacy interface for use in a mobilerobot in accordance with one embodiment of the present invention;

FIG. 5D depicts a schematic view of a privacy device in accordance withone embodiment of the present invention;

FIG. 6A is a schematic block diagram of internal architecture andrelationships between components in a mobile robot in accordance withone embodiment of the present invention;

FIG. 6B is a schematic block diagrams of alternative electronic systemsfor a mobile robot in accordance with the present invention;

FIG. 6C is an interaction state diagram for a mobile robot in accordancewith one embodiment of the present invention;

FIG. 6D is an interaction state diagram for a mobile robot in accordancewith another embodiment of the present invention;

FIG. 7A depicts a generic interaction algorithm in accordance with oneembodiment of the present invention;

FIG. 7B depicts a dialog algorithm in accordance with one embodiment ofthe present invention;

FIG. 7C depicts a bump algorithm in accordance with one embodiment ofthe present invention;

FIG. 7D depicts an interaction algorithm utilizing a combination ofvoice prompts and responses with display backup in accordance with oneembodiment of the present invention;

FIG. 8A depicts a networked server for a mobile robot in accordance withone embodiment of the present invention;

FIG. 8B is a schematic diagram of network protocols, security, andtransport layers in accordance with one embodiment of the presentinvention;

FIG. 8C depicts a schematic diagram of authentication and negotiationfor NAT/firewall traversing connectivity in accordance with oneembodiment of the present invention;

FIG. 9A is a reporting procedure algorithm for a mobile robot inaccordance with one embodiment of the present invention;

FIG. 9B is a communication system for a mobile robot in accordance withone embodiment of the present invention;

FIG. 10A depicts affect expressions for robot screen display inaccordance with one embodiment of the present invention;

FIG. 10B depicts affect movements for a robot in accordance with oneembodiment of the present invention;

FIG. 11A depicts a schedule graphic in accordance with one embodiment ofthe present invention;

FIG. 11B depicts a regimen initiation algorithm in accordance with oneembodiment of the present invention;

FIG. 11C depicts a regimen compliance algorithm in accordance with oneembodiment of the present invention;

FIG. 12 depicts a video/teleconference request algorithm in accordancewith one embodiment of the present invention;

FIG. 13A depicts a plan view of a home environment in which a robot ofthe present invention operates;

FIG. 13B depicts a robot-constructed topological map of the homeenvironment of FIG. 13A;

FIG. 14A depicts a plan view of a path traversed by a mobile robotduring a locating behavior, in accordance with one embodiment of thepresent invention;

FIG. 14B depicts a locating algorithm in accordance with one embodimentof the present invention;

FIG. 15 depicts a proximity algorithm in accordance with one embodimentof the present invention;

FIG. 16 depicts a regimen compliance algorithm in accordance withanother embodiment of the present invention;

FIGS. 17A-17B depict matching algorithms in accordance with embodimentsof the present invention;

FIG. 18A depicts a regimen compliance reminder algorithm in accordancewith another embodiment of the present invention;

FIG. 18B depicts a medication loading algorithm in accordance with oneembodiment of the present invention;

FIG. 19 depicts an algorithm of a first mode of multi-mode navigationfor a robot in accordance with an embodiment of the present invention;

FIG. 20 depicts an algorithm of a second and a third mode of multi-modenavigation for a robot in accordance with an embodiment of the presentinvention;

FIGS. 21A-21B depict a map generation algorithms in accordance withembodiments of the present invention;

FIGS. 22A-22C depict user interface displays for the mode of navigationdepicted in FIG. 19; and

FIGS. 22D-22F depict user interface displays for the mode of navigationdepicted in FIG. 20.

DETAILED DESCRIPTION

One embodiment of an autonomous mobile robot 10 is shown in FIGS. 1A and1B. The robot 10 has a body 12, one or more wheels 14, and a head 16.Certain components of the robot 10 (e.g., the body 12, wheels 14, andhead 16) may each be configured to be readily mounted and demounted fromthe others via compatible quick-mount and/or electrical contact pointarrangements, permitting different versions of each to be used in acompatible manner. A number of peripheral devices may be mounted on therobot 10, either on the body 12, head 16, or elsewhere. The depictedembodiment includes a touch screen 18 for allowing a user to interactwith the robot 10, answer questions posed by the robot 10, or give therobot 10 commands. A speaker 20 or other sound-generating device islocated on the robot 10. In addition, as shown in FIG. 1B, the robot 10may utilize a number of sensors 22 mounted on virtually any location onthe robot 10, for sensing various environmental conditions. For example,the sensors 22 may include cliff or edge detectors, vibration sensors,temperature sensors, cameras for visual sensing, tag detectors, laserdevices for proximity sensing, wall-following, or docking with a powersource or base station, detectors for following homing beacons or localenvironment indicia, etc.

For the purposes of this description, the robot has several categoriesof functional systems. Each functional system may include componentssuch as sensors; effectors (actuators); communications; andcomputational control. The robot described herein has severalapplication systems, where an application system is a system forachieving an overall function to be performed by the robot. For acompanion robot, there is necessary overlap with the human/robotinteraction system, as enhanced human/robot interaction is a primaryfunction. The robot includes systems (privacy protection, interactionsystems) to increase user trust and emotional attachment, which hasgeneric benefits by itself and increases the success rate of any and allother applications. The robot maintains a schedule or schedules ofhealth, hygiene, and or need-specific regimens, reminders, messages, andencouragement techniques for associated users.

The robot is responsive to voice command, touch on screen or surface;detection of movement and human presence and (other stuff); and therobot may communicate via voice synthesis, gestures, earcons, text,images, movement, and “ambient” color response. The form of the head andtorso of the robot may be designed to provide shrugging, nodding, headshaking, looking away (change of subject) and other gestural cues; themobility system permits approach and recede motions (personal space andconversational attention cues); and a facial matrix panel may permit afull range of facial expressions. A chest panel may be an interface to acontent player/engine. Low-level behaviors of the robot may accommodateinterruption by a person. One embodiment may employ a scripting enginethat can interrupt or be triggered by behaviors, and an alternativeembodiment contemplates that some behaviors, such as self-play, rescuerequests, gestural cues, can be executed as concurrent/arbitratedbehaviors. The robot may include a wheeled mobility system such as twodrive wheels and a passive caster, responsive to short-range objectavoidance and hazard management behaviors. The wheeled mobility systemmay also be also responsive to mid-range obstacle avoidance planning(path planning according to a SLAM generated map) and long-range goaloriented planning.

The head 16 may be mounted on a riser 13, stalk or neck. A turning (orpan) axis A_(P) runs generally parallel to and within the neck. Anodding axis A_(N) is transverse to the pan axis A_(P) and maysubstantially bisect the head 16. A display axis may be generallytransverse to and intersect either or both of the nod and pan axes, andmay project normal from the display 26. The head 16 also contains adisplay 26 used for facial animation, and which may be adapted forvideoconferencing, multimedia applications, menu input, etc. As shown inFIG. 1B, the head 16 of the robot 10 may also contain one or morecameras 28 which serve various functions, from navigating the robot 10around an environment, observing a resident or other person, acting as avideo phone or other communication device, etc. An antenna 30, modem, orother wireless communication device allows for communication between therobot 10 and a remote device, base station, etc. The teleconferencingcamera(s) 28 may also be considered navigation cameras 29 and used fornavigation, feature extraction and the like, or one or more separatenavigation camera(s) 29 may be separately provided (as shown in FIGS.3A-3B, for example, pointed at the ceiling to observe ceiling features,edges, shapes, or fiducials; or as indirectly shown in FIG. 22F, pointedat the floor or ground plane and including the robot's leading edge orleading portion).

The head 16 may be generally shaped as a sphere or other solid ofreasonably constant diameter (which permits the head to be seated oraccommodated in a neck or shoulder cavity with small enough spacing toavoid catching fingers between the head and neck joints or torso).

The head 16 may be articulated via a pan joint 315 including a pan motorand position encoder 314 and a tilt joint or hollow pivot 302 includinga tilt motor and position encoder 340. Either or both of the pan andtilt joints may be yoke-type joints, which has particular advantages asdiscussed herein. In the embodiment shown in FIG. 4, for example, thetilt joint 302 is a yoke-type joint, which permits a face matrix panel26 to be rotated to face into the neck (i.e., disappear from view) andthe rear portion of the head 16 to be rotated to take the place of theface matrix panel 26. Alternatively, a differential drive mechanismusing one motor and a clutch may be used to drive the head about twoaxes.

The torso or riser 13 (riser in general, to lift sensors and/or headelements to a height where the perspective of cameras and sensors isuseful for obstacle detection and remote teleoperation) may support thehead 16 and pan joint 315. The robot 100 includes the majority of thecomponents in the head 16 or mobility platform 12 rather than in thetorso 13 as an aesthetic and functional choice. Locating components awayfrom the torso 13 permits the robot to avoid a ponderous trash-canappearance. Functionally, there are several benefits. Heavier componentsare placed in the mobility platform 12, lowering the center of gravity.The torso 13 can more easily permit variable elevation or extension(pivoted/jointed/folding or telescoping torso parts) if few componentsare placed there. The mobility platform 12 supports the torso 13, andmay be generally triangularly shaped, or may be shaped as a curve ofconstant width (i.e., Reuleaux polygon with an odd number of sides).Optionally, the robot 100 fits within a generally pyramidal ortetrahedral envelope, with the mobility platform 12 generally extendingalong a bottom face, the torso 13 generally extending along one or twovertically angled faces, and the head 16 generally positioned at theapex. In this configuration, much of the internal volume of the envelopeis open, and may accommodate a carrying tray or a retracted manipulator(not shown). Additionally, the torso 13 can be arranged to extend fromone end of the mobility platform 12 toward the horizontal middle so thatthe weight of the head 16 tends to contribute to locating the center ofgravity in the middle of the mobility platform 12. The target height forthe center of gravity is approximately 30 cm from the floor (notnecessarily at all times if the head can be elevated).

In a particular embodiment, the head 16 of the robot 10 may serveseveral functions. The head 16 may include the main control board (anexample E20 shown in FIG. 6B, which includes a number of circuits andsubcircuits). The cameras 28 (charge-coupled device (CCD) orcomplimentary metal oxide semiconductor (CMOS) sensors with compatibleoptics) are provided for stereo vision (if two are used), and apyrolytic (heat-sensitive) sensor (S21) may directed along the directionof the display 26 (one or more of which may also be placed in a fixedlocation on the torso or base, pointing forward, sideways, and to therear). Cameras 28 may be located proximate (in this case, less than fourinches from) animated matrix or segment “eyes” 304 near the display 26,such that a person looking at the robot's head and eyes during ateleconferencing session will be regarding the cameras, and a remoteuser observing the teleconferencing session will see the residentlooking straight into the camera. While it is natural to look at “eyes”during a conversation, especially when the robot 10 acts as an avatar,channeling a remote user, it is unnatural to look at a camera (except,perhaps, for actors), and teleconferencing sessions generally have mostparticipants looking away from the camera. Placing the cameras within afew inches of the robot's animated eyes “304”, but not within them, mayresult in users of the robot seeming to essentially looking directlyinto the cameras 28 when in a video chat or teleconference. The cameras28 should not be in the eyes “304” in this embodiment, such that theentire “eye” 304 can be fully animated, or in different positions ondifferent faces displayable on the facial matrix panel.

The rear portion of the head 16 may be smooth and/or translucent, have arounded or other outer shape, may include indicia or ornamentation, ormay incorporate an additional informational display panel. A microphone32 may be included to collect audio data, receive verbal commands, etc.Preferably, a vectoring microphone array 305 is provided, with multiplemicrophones capable of locating sound sources and removing ambient noiseusing time of arrival and other filtering techniques. The display 26 maybe affixed to a main printed circuit board (PCB) housed within the head16. The PCB may include most of the control electronics of the robot 10,or a second PCB may be mounted parallel to the first PCB. The main PCBmay include Low Voltage Differential Signaling (LVDS) interface elements(E10 in FIG. 6B), and may be connected to compatible LVDS interfaceelements E10 in the body 12 via multiplexed LVDS wire pairs. Connectorsand cabling compatible with high frequency LVDS signaling may be used tocarry the LVDS signals between the main PCB and the body 12 as shown inFIG. 6B. The target cabling and connector impedance may be a 100 ohmdifferential pair. The use of LVDS may also simplify system wiring andreduce radiated emissions.

The body 12 of the robot 10 may be supported on three wheels 14 thatprovide stable three-point contact with or without use of a suspensionsystem. The three wheels 14 may be arranged with two differentialforward driving wheels and a rear caster, or vice versa; a greaternumber of wheels could distribute driving and idle wheels differently. Aharmonic drive, direct drive, or conventional gear train may be usedbetween drive motors (FIG. 4) and the wheels 14. The wheels 14 may besized to overcome about 3 cm high thresholds and may have a radius ofabout that size or higher. The size of the wheelbase W (approximately 32cm between wheels, in a particular embodiment) may be a function ofnecessary stability, and a lower center of gravity or larger number ofwheels may permit a shorter wheelbase.

The wheels may be alternatively holonomic or omnidirectional wheels.Such systems are disclosed in U.S. Pat. Nos. 3,876,255; 4,223,753; and5,374,879, the disclosures of which are hereby incorporated by referenceherein in their entireties. The robot may alternatively use as few astwo wheels with inverted pendulum dynamic balancing (depicted, forexample, in FIGS. 3A-3B). In some arrangements, the robot may useobstacle-climbing or cluster wheels as described in U.S. Pat. Nos.6,535,793; and 3,348,518, the disclosures of which are herebyincorporated by reference herein in their entireties.

Other components may be included on the robot 10 that provide additionalfeatures and functionality to facilitate bonding between the robot 10and one or more residents or users. “Resident” is used to describe aperson that lives in a home with the robot; unless used otherwiseherein, the terms “resident” and “user” may be used interchangeably. Aresident could be an elderly person or child who requires additionalattention or supervision, various members of a family, the family pet,guests to the household identified by residents, etc. To increase thelikelihood of bonding between the robot 10 and resident, the robot 10may include tactile sensors 34 or “digital skin” over any or all of itsbody 12 or head 16. These tactile sensors 34 allow the robot 10 torecognize when a resident is touching it (and respond appropriately tosuch touching). The tactile sensors 34 may also allow the robot torecognize when a resident is using a robot not designed to physicallyassist the resident for support, and appropriately react (immobilizingand sending an audio warning); such a striking function may serve as anemergency shut down, should the robot 10 be malfunctioning.

The head 16 may be mounted to a moveable neck, or a neck may be rigidand unmovable, and serve as a base for the head to move thereon. Acombination of both a moveable head and a movable neck is alsocontemplated. The moveable head 16 allows the robot 10 to interact morenaturally with a resident. In one embodiment shown in FIGS. 1A-1B and5A-5B, the head 16 is supported in a cavity 24 a by a hollow shouldersupport 12 a. A rotatable yoke within the shoulder support 12 a is ableto rotate around the turning axis A_(T). The yoke also allows the head16 to rotate about the nodding axis A_(N), so the display 26 may behidden from view under certain conditions (see FIGS. 5A and 5B). Also,movement of the head 16 allows movement of the camera 28 and display 26located thereon, giving the robot 10 both a wide range of camera visionand a wide range of display viewability. In a particular embodiment, thearticulated head/neck combination provides four degrees of freedom.

In one embodiment, display 26 is a facial segment or matrix panel and isa monochrome, backlit or non-backlit liquid crystal display (LCD)including between about 100 and about 1000 segments individually shapedas portions of facial features on a neutral gray field. The LCD may be asquare, rectangular, octagonal, etc., approximately 10-15 cm across,with a permanent pattern of segments. Neither the refresh rate nor theupdate rate need be rapid. Any subset of the segments can be on (i.e.,dark) at any instant, and segments can change or switch state in about50 milliseconds to about 1 second. The LCD glass is considered part ofthe head 16, and the display 26 should move as little as possiblerelative to the head 16.

The display 26 implements an eyes-brow-nose-mouth object display whichis animated in synchronization with speech and interaction to expressthe changing affect and non-verbal behavior of the robot 10. The display26 may be only backlit during interaction with a resident, if thebacklight consumes a more power than desired. Alternatively, the display26 may be a reflective panel, or backlit by ambient room light filteredin through the (translucent) head 16, backlit by one or more white lightemitting diodes (LEDs) and an appropriate diffuser, or any combinationof these. The display 26 also may be an organic light-emitting diode(OLED) panel, which may require no backlight (although one may be used)and could consume less power if light-on-dark facial patterns are used.

For a robot 100 provided with the facilities discussed herein, powerconsumption from two backlights can be half or more of the powerconsumed by the robot 100 at any time, and can restrict the operationtime of the robot to 2 hours or less (conversely, operating without anybacklight could increase this time to 4-5 hours).

The display 26 may be constructed using reflective bistable(non-volatile) technology such as electrophoretic, electronic balltwisting, electronic ink or electronic paper displays, and/or hybridelectronic ink/active matrix displays. Electrophoretic or electronic inkdisplays are made by a high-contrast, low-power technology that isbistable and retains an image when unpowered (e.g., E-Ink™ highresolution matrix Imaging Film or segment Display Cells from E-InkCorporation of Cambridge, Mass.; or electronic ink/gyricon sheets fromXerox/3M). This type of technology may have a switching time of about0.5-1 s, allowing for satisfactory display of caricatured facialexpressions. Hybrid electronic ink/active matrix displays combine a thinfilm transistor (TFT) active-matrix back plane, containing polymerelectronics-based pixel driving or conventional TFT technology on steelfoil, with a front plane of reflective electronic ink as above (e.g.,from SiPix Imaging of Fremont, Calif., or Polymer Vision of Eindhoven,NL). Display types operating on different principles, but that displayat least some of the identified characteristics (reflective ortransparent, very low power, bistable, etc.) are Fujitsu e-paperdisplays (cholesteric selective reflection film substrate-based colordisplay from Fujitsu, Japan), or NanoChromics™ displays (nanostructuredfilm electrode/electrochromic viologen molecule display from NTERA ofIreland).

When describing the display 26, the term “segment” panel means, in oneinstance, a panel made up of discretely shaped elements, rather than anX-Y matrix of pixels. The use of the term “matrix” panel means, in oneinstance, a panel made up of an X-Y matrix of pixels. The potentialbenefits of a matrix panel are that it can be used as an alternative (orthe sole) informational display, and that the faces or facialexpressions to be displayed thereon can be completely changed insoftware, downloaded, or user-designed. A segment panel, however, can besimpler and more efficient; can give extremely smooth outlines foractivated segments; and can be more easily adapted to user or communityprogramming of expression sequences.

While the description herein contemplates an octagonal or othermulti-sided polygon panel shape that permits covering most of thesurface area of a circular panel window 101 of the head 16, an ordinary4:3 or other rectangular LCD panel may be used in vertical or horizontalorientation. More than one panel can be used within the circular panelwindow 101 (e.g., three panels horizontally or vertically oriented canfill more of a circle than a rectangular panel). As shown in FIG. 10A,mouth, eye, and eyebrow objects can be arbitrarily formed from amultiplicity of pixels using a matrix display, or can be formed in setshapes from a number of segments using a segment display. Of course, apanel 26 may incorporate both segments and matrix portions, and matrixpixels can be considered one kind of segment. The segment or facialmatrix panel 26 may be provided with a sufficient number of segments orpixels by conventional manufacturing techniques.

Although the robot 10 of FIGS. 1A and 1B depicts two screens 18, 26,used for input and output, respectively, other embodiments of the robotmay utilize only a single screen for both functions, typically labeledwith both numbers (e.g., “18, 26” see FIGS. 3A-3B). For example, asingle touch screen may be used for both input and output viewing, andmay be located on either a head or a body of a robot. Alternatively, asingle display could be used for output, while input interaction withthe robot could be via a plurality of buttons, knobs, tactile or othersensors, etc. A tracker ball device or other type of contact pad formoving a pointer on the screen may also be utilized. The tracker ball orcontact pad may be located on the robot or remote therefrom.

An exemplary single-screen mobile robots are is depicted in FIG. 2 Thedepicted robot R2 may include a V- or U-shaped base 112, that allows therobot R2 to function as a walking aid or guide. The robot R2 includes atleast three wheels 114 for stabilizing a user who grasps and leans on apair of handles 136 (generally when a head 116 of the robot R2 is in ahorizontal position) in order to walk with the assistance of the robotR2, much like a conventional walker. The robot R2 may control therotation of one or more of the wheels 114 to steer the robot, or preventthe robot R2 and/or user from slipping or moving too quickly, and/or tomodulate the walking of a user, who may steer the robot R2 by turningthe head 116 via the handles 136. A torsion, angle, position, strain,and/or any other displacement detector may detect the twisting of thehead 116 relative to a stalk 124 or a track 134 (described below), andalter the movement of the wheels 114 so as to assist the person inwalking.

The stalk 124 includes a track 134, along which the head 116 moves 140(as depicted in FIG. 2). In addition, the head 116 may be rotatableand/or may swivel. The track 134 may be passive or motorized. The head116 may be fixed to a particular position along the track 134 by turninga tightening knob, for example, or may be automatically adjusted and/orfixed into position by a motor, locking bolt, cable, chain, rack andpinion, or any other system. The movement of the head 116 along thetrack 134 also may be effected by an electric motor under control of acontrol unit, for example, and may move in accordance with various robotbehaviors or functionalities.

Track 134 may have a top “dead center” position, such that at thetopmost point along the track 134, the head 116 may lie flat (i.e.,normal to gravity, G, optionally detected by an accelerometer,gyroscope, digital level, etc., in the head 116). Alternatively oradditionally, the head 116 may turn over to face a direction opposite tothe directions shown in FIG. 2A. As shown in FIG. 2A, the track 134 goesall the way to the ground, and a camera on the display face side orsides of the tray (head 116) may be moved to the ground position toprovide a ground plane view (for navigation, or for looking under sofasand the like for lost objects).

The robot R2 may include an display 126 on the head 116, which mayfunction as either a touch screen and/or visual output screen, asdescribed above. A speaker 120 may be located on the head 116 for audiooutput; a microphone 132 or array 132 may be utilized for audio input.Moreover, the robot R2 may include any appropriate sensors 122 or otheraccessories, such as a finger-cap heart-rate monitor, to provide medicalfeedback to a remote caregiver or doctor, described below. The head 116and/or display 126 may include one or more temperature, mass, weight, orother sensors, which may be used to detect properties of items placed onthe tray, or to facilitate appropriate use of the tray as a means tomove items from place to place (e.g., to detect too hot items, too heavyitems, or to detect items placed too far off-center). The head 116 maybe suitable for carrying or holding items (such as, for example, food orbeverages), and may include reactive, active, clamping, or passiveholder(s) or receptacle(s) for food, beverages, and/or medications.

FIG. 2 also illustrates an example of a mobile robot R2 that is equippedwith safety features. The speaker 120 may function as an annunciator forthe robot R2, or the robot R2 may include another “noise-maker,”(including gears or other machinery that are selected to be more noisythan necessary). The speaker 120 may be used in combination with aparticular audible profile, in order to audibly alert a resident orother people to the presence of the robot R2. The presence warningemitted by the speaker/annunciator 120 may be a periodic beeping, acontinuous tone, a bar of music, a soothing sound, or any otherappropriate notice which alerts people audibly to the presence of themobile robot R2. However, the noise should not be loud or intrusive. Inone embodiment, it is audible in about the same loudness range asordinary footsteps on a floor. In addition, one or more visible beacons138, such as a spinning light bar, may provide supplementary visualwarning. The visual signal emitted by the beacon 138 may be flashinglights, strobes, a continuous or changing beam of color, an imagedisplayed on the display 126, or any other appropriate visible signalwhich alerts people to the presence of the mobile robot R2. The visiblesignal may also be passive, e.g., reflectors or retroreflectivepatterns.

FIGS. 3A-3C depict several variations R3-R7 of a robot according to theembodiments of the invention. Each of the robots R3-R7 may include RFcommunication and may use the robot base station (shown here as BS,positioned atop a set top box STB described below).

The robot R3 balances on two coaxial wheels (or a ball) using invertedpendulum balancing (i.e., active or dynamic balancing via servo controlof the wheels using gyroscopic sensing), and is self righting. Near thetop of the robot is a display or teleconferencing screen 18 as describedherein. On top of the robot, pointing at the ceiling, a combinationcamera 28, 29 handles teleconferencing functions and navigationfunctions. The combination camera may be oriented at the ceiling forfollowing ceiling and/or light fixture and/or door and corner edges,features, indicia, or fiducials, and may be tilted by, e.g., 90 degreesto face forward for teleconferencing or additional modes of navigation.More than half of the weight of the robot is arranged near the wheels,such that the center of gravity of the entire robot is as close aspossible to the axis of the wheels or ball. Because the tipper ring 12,at knee level or above, is significantly larger than any part of thebottom of the robot, it may be less likely that the wheels or toe-levelportions of the robot will be tripped on. Similarly, the tipper ring iscircular and as wide as a person (e.g., 16-24 inches, preferable about18), and at knee height will encounter most table and chair legs.

The robot R3 may include an inertial sensor near the middle of theheight of the robot (3-4 ft.) such as an accelerometer, which may detectcollisions. At the top of the robot, a self-righting platform isprovided. The platform is also preferably dynamically balanced tomaintain a horizontal orientation, such that items carried thereon willnot tip or spill. Additionally, object detection and avoidance sensorsare positioned at the top of the robot R3. The platform supports amedication dispenser 17. As shown, the medication dispenser is acircular carousel of slots, each slot holding a small paper cup suitablefor containing pills or a “Dixie” cup suitable for a swallow or so ofwater. The dispenser or pill station may be fixed, rotatable manually,or by motor. The dispenser may include a movable D-shaped “purse” handle(not shown) and may mount and dismount from the robot, and or lock tothe robot. The dispenser may also fit into a loader, which may bepositioned at another location in the home (e.g., in the bathroom,networked, and containing a magazine of pills for loading thedispenser). Loading techniques discussed herein may use a pre-filled(off-site, at a pharmacy, etc.) magazine type loader to load thedispenser. As shown, the dispenser MD or 17 may also be positioned atanother location in the home.

No one or more components are necessary. A variant R5 is essentiallyalike, but includes an extending or telescoping riser 13A (usingtelescoping barrels, jacks, screws, scissors, or an articulated and/orjointed arm), such that the medication dispenser 17 or other componentscan be moved about the house with a lower center of gravity. A variantR4 omits the display 26, 18 and dispenser 17, but still includes anavigation camera 28 and many remaining facilities. Such a robot R4, inomitting a display screen, may guide the resident to a set-top box STBand television for vide chat purposes. That is, for those robots whichdo not have a teleconferencing camera 28, or even for those that do, aset-top box STB may form a part of the robot system. The set-top box STBmay be integrated with the robot base station or a separate componentprivileged on the robot base station network. As noted, the base station(and possibly the STB) are located in the home at the broadband ingress(typically cable, xDSL modem or fiber optic terminal, but also WANwireless networks). As shown, the set-top box includes ateleconferencing camera directed toward a position in front of a TV uponwhich the set-top box STB is most likely positioned. Because a normalhousehold television screen is much larger than any screen that can becarried by the robots R3-R7, in a teleconferencing mode (that may betreated as a regiment event for the purpose of scheduling and bringingthe resident to a regiment compliance object—the STB and TV—as discussedherein), the robot may bring the resident to the STB and TV for avideoconferencing session that takes advantage of a large screen (on theTV), stable acoustics (a microphone array on the STB that is not subjectto motor and mechanical noise), stable AC power, a stable camera, andwired broadband access.

Two further variants are shown in FIG. 3B and FIG. 3C. The mobilitysystem of the robot R6 of FIG. 3B uses three pairs of wheels front toback (six wheels in total), in which the center wheel pair is slightlylower than the outer two pairs. This permits low friction on smoothsurfaces, good traction on soft surfaces, and ready turning in place onmost surfaces. The display 26, 18 takes the form of tablet computer formpad, removable from the robot as necessary, but oriented similarly tothe other embodiments discussed herein when the robot R6 is normallynavigating. The display pad 26, 18 itself would have a separate wirelessconnection to the base station BS. The navigation camera 28 ispreferably not be on the pad 26, 18, although a teleconferencing cameramay be (through which one could find a dismounted pad). The medicationdispenser in this case is a dismountable chest or kit, and may be “hung”on the robot and engaged thereto. The “head” 16 in this case isprimarily for mounting the display pad 26, 18 and medicine chest 17.

The mobility system of the robot R7 of FIG. 3C uses a differential driveand front or rear caster similar to household robotic vacuums. Aninverted cone, largely empty in the middle, leads up to the tipper ring152, configured as discussed herein. In the middle of the tipper ring,the medication dispenser 17. In this case, the medication dispenser 17essentially hangs, pivoted and free to swing, (remaining essentiallyhorizontal at most time) within the cone and center of the tipper ring152. The medication dispenser 17 may also be actively controlled to stayhorizontal. The variant of R7 may be the least costly discussed herein,and may navigate semi-randomly (with wall following and other chamberdiffusion techniques) or with limited recording of doorways and thelike, being able to identify its proximity to the resident, usingproximity and presence scores as noted herein, but using no maps. Inthis case, the R7 variant would start trying to find the residentearlier than the other variants, e.g., from 15 minutes to an hour beforea regimen event. This robot R7 may have tag or lighthouse basednavigation, and may communicate with a pill station or medicationdispenser 17 not on the robot R7 by infrared. The medication dispensermay be replaced with, or have underneath it, a net for holding andcarrying various objects. Again, the tipper ring 152 is of largerdiameter than the base. The base station BS may be RF-connected, but inthis case may also be alternatively connected to a regular phone line,and provide only limited data services (and may then be remotelycommunicated with indirectly by caller ID channels, tip and ring, andother phone line signaling).

FIG. 1B, as noted, depicts the embodiment of the mobile robot R1, havinggenerally a triangular base 40, a lengthened body 12, and a head 16 atthe top of the body 12. In this embodiment, the head 16 includes a yokeassembly 42 allowing for movement. The robot R1 includes wheels 14,sensors 22, at least one camera 28, and one or more screens 18, 26. Themotors 22 are located proximate the wheels 14. Additionally, mainpower/control components 46 are located in the base 40. Location of thepower/control components 46 may vary as desired for a particularapplication. In certain embodiments, the power/control components may besplit into a power component and a control component, with the powercomponent located in the robot base or body, and the control located inthe head.

FIGS. 4A and 4B illustrates an example in which object detectioncoverage is provided by a plurality of converging infraredemitter-sensor elements, arranged in zones. Of those sensors, severalface down for cliff sensing, several face forward, some face backward,and a number are special configurations described herein. This sensorsystem may function alone, or, as an alternative, may function incombination with one or more bump switches for redundancy, for example.

In accordance with one example configuration, the robot 100 includes sixinfrared rangefinders for obstacle and stairwell avoidance, with threebump switches for obstacle avoidance when backing up.

The infrared sensors preferably have a similar electronic implementationsuch as, for example, a synchronous reflectivity emitter/detector paircomparable to cliff detectors. With regard to the infrared rangefinders,as non-limiting implementation examples, emitter/detector pairs may bedeployed in accordance with several different configurations as follows:Convergent-Crossed emitter/detector pairs 965 are emitter/detector pairsproviding a specific detection zone at the point of intersection, asused in cliff sensors. Diffuse-Parallel 966, 962A, 962B are colocatedemitter/detector pairs preferably providing a 30° field of view(+/−15°), detecting objects at distances between (for example) about 2cm and 20 cm, depending upon the reflectivity of such objects. TheTangential sensor 961 may utilize a “broken beam” topology createdacross a concave surface 978 at the front of the robot 100.

In accordance with at least one configuration, as non-limiting examples,the sensors can perform synchronous detection during and afterillumination pulse of associated emitter; in which each sensor readingproduces two scalar values denoting ambient reflectivity and illuminatedreflectivity. With a least 8-bit dynamic range, each sensor can produceat least 100 such samples per second. In a preferred configuration,analog conditioning/filtering/integration is done on each detector'ssignal before moving into the digital domain. Further, the detectorcomponents may be standalone photodiodes, or may integratetransimpedance amplifiers to improve the signal-to-noise ratio through awiring harness. A robot 100 including 16 such sensors is shown in FIG.4B, for example.

A preferred configuration relates to a robot including sixforward-facing diffuse sensors 966, spaced 7 cm apart, which can providesensor coverage for objects up to about 14 cm away, provided that theobjects are reflective enough to be detected at that range. Threedownward-facing cliff sensors 965 are placed before each wheel 14 in itsdirection of travel. Two angled diffuse sensors 962A, 962B and 963A,963B at the rear-angled sides of the robot mobility base 12 provideobstacle detection in the reverse direction, and can guide the dockingprocess in conjunction with matching emitters on the dock, for example.Two angled convergent sensors 966 at the front provide a defineddetection zone just outside the projected envelope of the robot, for usein wall following and wall locating, for example. A tangential beamacross the front 978 of the robot base provides precise contactinformation when an object touches any part of that surface, and mayaccordingly accelerate collision detection and accurately locate theobject's position.

Because the mobile robot 100 functions in a household environment, theissue of household safety may be addressed by any of a variety offeatures. Among these features, inter alia, are personal contactavoidance, obstacle avoidance (including the ability to detect and/oravoid objects that exist over a wide range of possible heights andpositions relative to the robot 100), and damage avoidance—avoidingand/or mitigating damage to either the home, objects in the home (suchas furniture, fixtures, and the like), or the robot itself, for example.In connection with these features, the robot preferably includesredundancy in detecting and/or avoiding obstacles.

Regarding personal contact avoidance, the robot 100 preferably avoidsinitiating physical contact with any person—such as the user—unlessthere are circumstances that make such contact unavoidable or necessary.However, as non-limiting examples, the robot 100 may initiate contactwhen a possible medical emergency requires the robot to measure thetemperature of the user, or when an authorized remote user issues acommand to the robot to make physical contact with a person, inter alia.

In accordance with at least one aspect, the robot 100 includes one ormore sensors for detecting the presence or absence of objects over arange of physical space, in which the monitored space is divided intoprotection zones. As illustrated in FIG. 4C, for example, the areasurrounding the robot 100 includes a “toe zone” Z10 ranging from groundlevel up through about two inches above the ground; a “bump zone” Z20ranging from about two inches up through about 4 inches above theground; a “near zone” Z30 ranging from about one inch up through about12 inches above the ground; and a “face zone” Z40 corresponding to thearea directly in front of the face 26 of the robot, and which varies asthe face 26 is raised or lowered, or as the face 26 swivels or rotates.Each protection zone is monitored by at least one sensor (such as, forexample, a photosensor or a bump switch), and preferably there isoverlap of the monitored zones among two or more of the sensors. As aresult, the redundancy of obstacle detection is improved and thelikelihood of an obstacle failing to be detected is reduced, becauseeven if an obstacle is not detected by one of the sensors monitoring anoverlapped area, another sensor monitoring the same overlapped area maynonetheless detect the obstacle.

As illustrated in FIG. 4C, the bump zone Z20 is monitored by a bumpsensor 957, such as a contact switch or pressure sensor. The near zoneZ30 is preferably monitored around a full perimeter of the robot 100, by(for example) a light curtain that may include beam emitters L21, L22and photosensors 956 that detect light reflected off of objects that wasemitted by the beam emitters L21, L22. Objects between 2-4 inches abovethe ground may be detected at between 1 to 5 inches laterally outwardfrom the robot 100, for example. Low objects such as toes or doorthresholds may also be detected. Also, one or more cliff sensors may bepositioned around the mobility platform 12 and detect any sudden orprecipitous drops in ground elevation over the full perimeter of therobot 100.

In the area in front of the robot 100, the light curtain may detectincursions by objects at a height between approximately one through 12inches above the ground. Toward the face 26, the near zone Z30 may alsobe monitored by an infrared or ultrasonic obstacle sensor. At far range,such as two through twenty feet or more, the robot 100 may include acamera 304, which can detect both near and far objects when imageprocessing is applied to the data produced by the camera 304.

In order to detect people in front of the robot 100, heat sensors,ultrasonic object sensors, or voice vector detector arrays may be used.For example, the robot 100 may include an array of six microphones (notshown) positioned such that the direction of the source of a sound maybe determined; when the robot “hears” sound that corresponds to speechand the voice vector array indicates that the source of the sound is infront of the robot, the robot may respond accordingly. In addition, therobot 100 may employ such “people detectors” at either side and/orbehind the robot 100, in order to detect people who may be standing orapproaching too close to the robot (such that a danger of collision orof the robot tipping), in order to respond appropriately.

The robot can receive data from two or more sensors, integrate thesensor data to predict the likelihood of an obstacle being present inone of the protection zones, and modify its actions (for example, byreducing speed, changing the direction of travel, and/or lowering thehead 16, inter alia) when the predicted likelihood of an obstacle beingpresent exceeds a threshold. Moreover, the threshold can be adaptivelymodified in accordance with experience—for example, when the robotcollides with an obstacle after failing to predict the presence of thatobstacle, the robot can lower the threshold; or when the robot discoversthat a predicted obstacle did not in fact exist, the robot can raise thethreshold.

As an advantage, by predicting the presence of an obstacle coming intothe path of the robot based on input from more than one sensor and/ormore than one protection zone, the robot can avoid or mitigate obstaclesencroach onto a primary protection zone.

As illustrated in FIG. 4C, for example, the face 26 of the robot mayinclude a forward-directed camera 304 that monitors and can detectobjects over a broad range of distances in front of the camera 304. Therobot 100 may also include a first beam source B21 that emitsdownward-directed beams of light L21 and a second beam source B22 thatemits upwardly-directed beams of light L22. The beams of light L21 andL22 preferably intersect over an area, and when either beam contacts anobject, light is reflected off the object and is detected byphotosensors; the range of space monitored by the beam sources B21, B22and photosensors 956 generally corresponds to the near zone Z30. Thedifferent beams of light L21 and L22 may have mutually differentwavelengths, or may be encoded with different signals, for example, suchthat the reflected light detected by the photosensors 956 can determinewhich beam source B21 or B22 emitted the reflected light. When thecamera 304 detects a possible object lying near the lower area of theface zone Z40, and the photosensors 956 also detect light reflected offof an object, the robot 100 can determine that the likelihood of anobstacle in the near zone Z30 is high, and halt the robot 100 frommoving forward in order to avoid colliding with the obstacle, forexample.

In addition, the robot 100 may include a microphone that monitorsambient sound or noise levels. When the microphone input indicates soundcorresponding to speech, for example, the robot may determine that it islikely a person is in the vicinity, and accordingly reduce its movementspeed, in order to reduce the chance of colliding with the person. Therobot 100 may also monitor other sensors such as heat detectors(infrared photosensors, for example) or cameras, and make behaviordeterminations based on one or more of the sensors. For example, if noperson is in fact in the vicinity of the robot, but the television isturned on, then the robot's microphone detects speech, but the heatdetector does not indicate the presence of any heat sources. In such acase, the robot 100 may instead determine that no person is present, andaccordingly decide not to reduce its movement speed.

When the robot 100 is in an environment containing many potentialobstacles (for example, in a cluttered basement or in a room full ofpeople), the robot may operate at slow speed in order not to collidewith people or things. When operating at slow speed, the robot may relymore on bump sensor input than on optical cameras or photosensors, forexample.

The cameras on the robot, depicted for example, as item 28 in FIGS. 1Aand 1B, allow the robot to view a resident or other persons in anenvironment. Even if the resident is comfortable with an interactiverobot regarding them on a regular basis, the network connectivity (asdescribed below) of the robot may raise privacy concerns for residents.Residents may feel that they are being “watched” by a third person, orthat an imagined “hacker” may be able to view them in their home.Accordingly, the robot may be equipped with functionality that displaysor otherwise ensures that the privacy of the resident is not beingcompromised. This functionality includes, but is not limited to,camera/head position limitations, visible or audible indicia, or defaultconditions that prevent lapses in privacy.

FIG. 5A depicts a perspective and side schematic view of a movablecamera 28 in an operating position within the head 16 of a robot. FIG.5B depicts the same camera 28 in a non-operating position. Here, thecamera 28 includes a body 300, having a pivot 302 and a lens 304.(Alternatively, the entire camera 28 may be located behind a shield 306,which may completely enclose a void 24 a within the head 16.) Wires forpower and visual image feed are contained within a support structure,and may enter the body through the hollow pivot 302. Alternatively, thewires may be located external to the support structure, but would needto be long enough to allow unimpeded movement of the head 16. In FIG.5A, the camera 28 is directed outward, providing an unobstructed forwardview, in the operative position. The resident therefore may be able toclearly ascertain that the camera 28 is capable of recording (andpotentially transmitting) visual data. However, in the non-operatingposition of FIG. 5B, the camera 28 may be rotated or otherwisepositioned so as to face an opaque surface forming the hollow 24 a,which may encompass the entire field of vision of the camera 28. Anon-operating position depicted in FIG. 5B may alternatively function asthe default position for the camera 28, unless the resident grantspermission for the operative setting of FIG. 5A.

If utilized, a shield may be transparent to allow clear viewing of thecamera 28 within the hollow 24 a. Alternatively, it may be entirelyopaque and movable into a position to cover the camera 28, so theresident may directly control the ability of the robot to view andpotentially transmit visual data. In one embodiment, the camera and/orlens is entirely withdrawn into the robot's body, or the lens is turnedto abut the robot's body.

Accordingly, the robot is not only rendered incapable of recording itssurroundings, but can be readily confirmed as incapable of suchrecording, as indicated by the blocking of the lens, the turning of thelens to substantially face the robot's body, or the turning the head tochange the field of view. The visual cue of camera or head position maybe supplemented by an electronic light that may be dimmed or undimmedwhen the camera is recording visual data. Thus, the person can clearlysee and confirm that they are not under potential surveillance by athird person. A similar mechanism can be used with a microphone 305 ormicrophone arrays 305 on the robot; the robot may disconnect, shutter orotherwise disable microphones when entering a privacy mode. If themicrophone(s) 305 are turned along with the head or otherwise moved tobe blocked, an elastomer seal in the inoperative position may furthermuffle sound. Similarly, external antennae can be disconnected. In eachcase, the transmitting medium is rendered incapable of monitoring theresident.

As shown in FIG. 5C, a lockout mechanism may take forms other thanturning a camera 28 or microphone(s) to be isolated from the local area.In one model, the resident or user has verifiable, ultimate control overthe physical ability of the robot to monitor the local area. A key slot,plug, or other connector 321 capable of receiving a lock-out member(such as a key 322, dongle, etc.) is provided at a lock-out station 320readily accessible and visible on the robot 10. If the robot isconstructed under the model that the resident has control that may notbe overridden, the engagement of the lock-out member or key 322mechanically closes electrical contacts, enabling the camera 28 (andmicrophone) to operate, and completely disabling the camera andmicrophone in when in a private position. In an alternative arrangement,a lock-out member as a slider 333 including visible electrical pins 332is arranged in the lock-out station 320. The resident may readily verifythat the camera and microphone cannot work at all, because criticalelectrical paths are open. When the slider 333 is closed to a receivingplug 331, a notifier indicates a readily understood message (e.g., “onthe air”) or signal (e.g., flashing LED) giving notice that the robot isconnected to the world at large. This kind of arrangement, a privacymember configured to physically unplug the sensor when a privacy mode isselected, may give the resident a degree of confidence that thehousehold is “hacker-proof” with respect to camera or microphonesurveillance of the resident.

In an alternative model, the key slot, plug, or other connector 321 doesnot mechanically close electrical contacts, and can be overridden inemergency situations. In this case, software transmission controlroutines may enable transmission of surveillance data from the camera 28outside the resident's home only when the lock-out member is inserted inthe connector 321. In this model, the robot 10 may normally use itscontroller connected to the camera or microphone to monitor surveillancedata from that sensor. The robot may run a transmission control routineconfigured to enable transmission of surveillance data from the sensor(to the caregiver) outside the resident's home if the resident grantspermission for the transmission. However, an override routine may beconfigured to enable a transmission of surveillance data from the sensoroutside the resident's home (i) in an emergency condition detected bythe robot. Alternatively, if an authorized remote caregiver sends anauthorization previously permitted by the resident together with anemergency condition, the camera and/or microphone may be enabled.wherein the transmission of surveillance data by the robot outside theresident's home is otherwise prohibited. This kind of arrangement mayalso use a privacy member configured to physically unplug the sensorwhen a privacy mode is selected, if the override mode uses a mechanismor relay to “replug” the sensor.

In accordance with at least one embodiment, any sensor input capable ofobserving or monitoring the environment surrounding the mobile robot maybe routed by a privacy device 350, as illustrated in FIG. 5D. A privacycontroller 352 tracks any permissions granted or denied by the resident,and controls the data stream from sensors, such as the camera 28,microphone 32, or other sensor 22, thereby permitting sensor input to berecorded by the data recorder 356, and/or transmitted by the antenna 30to a remote data recorder, only if such recording or transmissioncomplies with the permissions granted by the resident. The privacycontroller 352 may be implemented as a discrete hardware item or as adivision of another piece of hardware; alternatively, the privacycontroller 352 may be implemented as a software routine. In oneembodiment, the privacy controller takes the form of a key, plug,dongle, or other physical medium that enables sensors only wheninstalled, e.g., as shown in FIG. 5C.

An override unit 354 may override privacy directives issued by, ormonitoring capabilities disabled by, the privacy controller 352, andthereby permit the sensor input to be temporarily recorded and/ortransmitted, despite the permissions implemented by the privacycontroller 352. In certain embodiments, the override unit 354 may onlyoverride the privacy controller 352 when either a predetermined event ispresent, the event being either a threshold on the output of one or moresensors or interpreted data as detected by the controller 352, or when acaregiver's override command is received by the mobile robot. Anoverride command from the caregiver may be in the form of an encryptedcode or other secure transmission, encoded or digitally signed using anysuitable method, such as, for example, digital certificates, public-keyencryption, a predetermined password, or any other suitable mechanism.

The override unit 354 may permit surveillance or monitoring temporarilywhen, e.g., a distress condition of pulse, breathing, medical,environmental, or safety monitoring sensors, or other emergencysituation is detected. When a distress condition is detected, the robotmay also make an outbound call requesting the caregiver to check on theresident. Also, the mobile robot may include a receiver for wirelesslyreceiving the override command (from a remote terminal, which may beoperated by a caregiver, for example). In addition, there may becircumstances in which considerations of safety or health suggest thatthe usual permissions granted or denied by the resident be temporarilyoverridden. Master override permissions may enable a caregiver toreceive permission to temporarily override subsidiary permissions inemergency situations, or to enable medical monitoring devices or dataanalysis conclusions to override these permissions.

Circumstances that may require overriding of the privacy controller 352may include a determination by the mobile robot that the resident hasbecome non-responsive (and therefore possibly unconscious), or when afire alarm or smoke detector has triggered on the robot, or in theenvironment. In such circumstances, the override unit 354 may overridethe privacy controller 352 to permit input from the camera 28,microphone 32, or other sensors 22, to be transmitted to a remoteterminal belonging to a caregiver, police or fire department, orambulance service. Therefore, the caregiver may be alerted to suchemergency circumstances, and receive relevant video, image, or audioinformation from the mobile robot in proximity to the resident.

FIGS. 6A-6D depict some of the software architecture, electronicsystems, and network connections of embodiments of a robot as disclosedherein. Not all of these is necessary in every robot discussed herein,but the description applies at least in part to each embodiment.

FIG. 6A shows a basic architectural distribution of tasks and functions.A behavior based robot acts largely on the basis of behavioral systems,in this case as depicted as reactive systems 6A-1. Short-rangenavigation is navigation within and among obstacles in a room, and wouldnormally be handled by a combination of cruising and turning behaviors.Goal behaviors seek, home in on, or search for relatively simplegoals—e.g., a charger, a virtual wall or lighthouse, a beacon, a sound,an area of strong signal reception. Escape behaviors enjoy higherpriority in the event of robot stasis, stuck, canyoning, or othertrapped conditions. Avoid behaviors may avoid simple hazards—cliffs,perhaps people. Wall following behaviors and other behaviors followobstacles to improve navigation and diffusion. All of these behaviorsare arbitrated and contend for control of actuators 6A-4, based upon acollection or suite of sensors 6A-5 (vision, stairwell or cliff,proximity, wheel encoder or other odometry).

Higher level planning is not always necessary, but can be handled byspecific controls that influence or direct the behavior based systems.As shown, the behavior bases systems normally intervene between planningroutines 6A-2 and actuators 6A-4. Long-range navigation, as discussedherein, will move the robot from room to room as discussed herein, oralternatively using path planning A mapper may build maps, which may ormay not be “Cartesian” spatial maps (most of the routines, techniques,and inventions discussed herein do not rely upon Cartesian or spatialmaps). Stereo feature extraction may proceed according to known routines(e.g., SIFT or SURF scale invariant feature extraction) in order toidentify landmarks or labels. Some of the necessary records may bestored remotely on a server or database 6A-3.

FIG. 6B illustrates one example of component organization in accordancewith at least one of the present embodiments, in which communications orpower transmission relationships are denoted by arrows interconnectingvarious component blocks. In one example, components located generallyin the head 16, neck or torso 13, or mobility base 12 may be organizedinto component clusters E20, E30 and E46, respectively. These componentclusters may include various electronic or electrical circuits, such aspower supplies, motor controllers, and/or integrated circuits.Preferably, components such as integrated circuits, CPUs, controllers,and communication buses are integrated onto PCB boards; as anon-limiting example, a robot 100 may include three PCB boards, in whichan upper PCB board E20 is disposed in the head 16, a middle PCB boardE30 is disposed in the torso 13, and a lower PCB board E46 is disposedin the mobility base 12.

In the example of FIG. 6B, non-power signals are preferably transmittedamong the upper, middle and lower PCBs via a low-voltage differentialserial channel (LVDS), which provides advantages of producing only lowlevels electromagnetic noise (and having low susceptibility toelectrical noise interference), inter alia. Alternatively, a parallel ortraditional serial bus (such as RC232) may be employed, or a wirelessprotocol such as WiFi or Bluetooth, in order to transmit signals betweenthe PCBs.

The lower PCB board E46 includes one or more power supplies E90 and abattery and/or charger E91, in which a power supply channel (which maybe a plastic-sheathed copper wire, or any other component suitable forpower transmission from the mobility base 12 through the torso 13 andinto the head 16) transmits power from the power supplies E90 to themiddle PCB E30 and to the upper PCB E20. The lower PCB E46 also includesa pan motor amplifier E401 and one or more drive motor amps E402,together with encoder E403 and proximity sensor interfaces E404, andalso a two-dimensional accelerometer E406 and a microcomputer E407(which may include a microcontroller, a programmable logic array, adigital signal processor, and/or a general-purpose CPU, as non-limitingexamples). The lower PCB E46 communicates with proximity sensors 222(routing such communication to the proximity sensor interface E404),drive motors/encoders 46, and to the pan motor/encoder 314.

Regarding the torso area, various features local to this region—such asthe body display panel 18 and speakers S31—communicate with the middlePCB E30. Also, an array of microphones may be disposed on the robot 100for determining the location of the source of a sound. In accordancewith at least one embodiment, a microphone for use in a sound-sourcelocating system (herein termed “Acoustic Magic”) preferably transmits acontinuous serial stream of octets indicating the direction of currentsound. The stream is transmitted by a DSP onboard an Acoustic Magic PCB,through its synchronous serial port, emulating an asynchronous serialsignal.

The serial signal is received by an HCS12 on the power board, and theoctets may be delivered unprocessed in the packet stream to the CPUboard.

On the CPU board, a process receives the signal and decimates it to (asa non-limiting example) 10 samples/second, storing the stream in ashared-memory ring buffer. The decimation is preceded by a single-poleIIR low-pass filter, with a pole at 3 Hz, for example. The bufferpreferably records at least the last 5 seconds of observations, each ofwhich are time-stamped with a true timestamp for when that audio samplewas actually heard (accounting for any buffering through the signalchain).

The estimated voice location is produced by combining this vector withthe speech detector of the recognition system. The speech detectorpreferably may issue regular callbacks indicating its live status. Thesecallbacks correlate detected speech (compensating to true real time)with the 10 hz voice location samples, to produce the estimateddirection vector to the most recent detected utterance. These utterancedirection vector samples are similarly recorded in a shared memory ringbuffer, for use by the user-location and interaction system. Suchfunctionality and processing is preferably provided by an arrayprocessor E301 disposed on the middle PCB E30.

In the head area, various sensors such as a pyro sensor S21 or touchsensor S22 may communicate with the upper PCB E20, as well as the rightand left image sensors (cameras, etc.) 28, 29, and the face matrix panel26. The tilt motor/encoder 340 also is connected to the upper PCB E20.

Within the upper PCB E20, components corresponding to devices disposedin the head 16 may be integrated onto the PCB board, such as: a facecontroller/interface E210, for interfacing with (and/or controlling) theface matrix panel 26; audio codecs/amplifiers E211; and/or EthernetE202, USB E203, or infrared (IR) E204 interface components forcommunicating according to their respective channels. Further, the upperPCB E20 may include an embedded microprocessor E230 (preferablyconsuming less than 1 Watt per hour) and a memory E209 comprisingvolatile and non-volatile sections, for providing necessary instructionsto coordinate and/or control the various subcomponents on the upper PCBE20.

In addition, the upper PCB E20 in the head 16 may be connected to anantenna E201, such as a cellular-band antenna for use with a CDMA modem,in which the antenna E201 includes an embedded antenna component mountedon a PC board. As an advantage, such components are designed forcellular handsets, are small, precisely manufactured andimpedance-matched, and easy to integrate. Further, the antenna designmay alternatively use simple wire dipoles to additionally reduce cost.

Preferably, a dipole design is implemented directly on the upper PCB E20in the head 16. One example cellular modem slot supports modulesoperating in the 800 mHz cellular band, specifically the transmit bandfrom 824-849 mHz and the receive band from 869-894 mHz. The robot's head16 may be selected to be large enough to accommodate a half-wave dipolefor these frequencies, which is nominally 163 mm long. However, if manyother mechanical and electrical components are packed into the head, theantennas may alternatively be mounted horizontally. As anotheralternative, an “inverted V” configuration may be used, which is ahorizontal dipole, extended slightly (by approximately 4%, for example)and bent in the middle. The inverted V has the added advantage of a moreuniform omnidirectional response pattern.

A preferred configuration places two “inverted V” dipoles, mounted atthe top and bottom of the head for spatial diversity. Each dipole hastwo legs, each preferably 85 mm in length, 2 mm in diameter. Thecalculated VSWR for this configuration may range from 1.7 at 824 mHz,1.2 at 860 mHz, to 1.7 at 894 mHz. These antennas may be implementedwith (for example) 12-gauge wire segments affixed to Plexiglas supportsplaced behind the CPU board, in which case 50-ohm coaxial cables canconnect the antennas to the CDMA modules.

FIG. 6C shows transitions between levels of activity in a robot during aday. Not all of these states are necessary in every robot discussedherein. Nor need there be divisions as shown. Largely, these states areuseful for power conservation. In a Sleep state for maximum powersaving, in which the robot neither “listens” nor “observes” itssurroundings (e.g., camera and microphones are disabled, Sleep state mayalso be considered a Privacy Mode) the robot may enter an Idle state(from which it may begin an interaction script or other activity) uponsome external or internal stimulus event. If the battery is fullycharged, the robot may rest in a Monitor state rather than a sleepstate, and may enter the Idle state upon any event detection, includingsound, heat, or observed or detected motion. The robot may move fromMonitor to Sleep state in a low battery charge condition or when nosound or motion is detected for a certain period, e.g., 10 minutes.Changing from Sleep state to Monitor state may be prevented withoutexpress permission. Similarly, the robot may enter the Monitor statefrom the Idle state in circumstances of inactivity or charge required.The Orb mode is a condition where the robot illuminates the area aroundit.

FIG. 6D shows transitions between different functions in a robot duringa day. Not all of these functions are necessary in every robot discussedherein. Nor need there be divisions as shown. The Sleep function andIdle function are similar to the states as discussed with reference toFIG. 6C. If the battery is fully charged, the robot may rest in a Global(Ready) function ready to undertake other functions, rather than a Sleepor Idle state, and may enter the Global function upon any eventdetection, including sound, heat, or observed or detected motion. Therobot may move from Global to Avatar function. In the Avatar function, ateleconferencing, teleoperation, or remote presence session may bestarted or activated from suspension. In a Companion function, adialogue as discussed herein may be started or activated fromsuspension. In an Application function, any application that is storablein a suspended state by saving a runtime stack may be started oractivated from suspension. In a Speaker Phone or video chat mode, therobot may start or activate a call.

FIG. 7A depicts a generalized dialog routine that may be used by a robotof the present invention for natural, flowing communication. Step SD1initiates a Start Sequence, where the robot may select one of variousconversations or dialogs to engage in with the resident. The sequencemay be selected based on an occurrence of an event or time. For example,the robot may initiate a greeting sequence when the resident returnshome, or may ask the resident if they have any plans for the eveningafter a meal occurs. Additionally, the robot may generate sequences atrandom, to increase contact and bonding opportunities with the resident.The robot may approach the resident and inquire if the resident may beinterested in playing a game stored on the robot, asked to be picked up,etc. Additionally, the dialog sequence need not occur between the robotand resident, but may include the robot talking to itself. In oneexample, if the robot bumps an object while moving in an environment,the robot may begin a sequence expressing surprise or frustration.

Step SD2 represents a first interaction, which, depending onapplication, may be a greeting to the resident, an audible comment toitself, etc. At Step SD3, the robot may ask the robot a question or makean affirmative statement, “How was your day?”, “Got plans tonight?”,“You asked me to check movie times for you.”, etc. The question bedesigned specifically to elicit one of a specific number of responsesfrom the resident, or the resident may respond to an open-ended questionor statement. A Response X (outside the robot's library of anticipatedresponses) may cause an error, confused, or other reply from the robot,Step SD, causing the robot to end the interaction or pose the questionor statement again, Step SD3. Predetermined or expected responses mayinitiate corresponding replies, Step SD5, from the robot. These repliesmay include a matching affect responses as well; e.g., an audible “Wow”with an affect indicating surprise, an audible “That's too bad” with anaffect indicating concern, “Sounds great” with a happy affect, etc.Alternatively, the robot's response may be a second question. Forexample, if the robot asked the resident which movie the resident wouldlike to see, the robot could then ask if the resident if the robotshould search for theaters showing that movie, and so on.

After the robot's reply at SD5, the robot may begin a number of secondinteractions, at Step SD6. For example, the robot may begin playing agame with the resident, move on to a second, more specific line ofquestioning or interaction, or end the interaction in view of particularresponses. Certain interactions may lead to other interactions. Underthese circumstances, the robot may interact with the resident for longperiods of time, changing topic, activity, or task, as the circumstancesdemand, creating a rich interactive experience for the resident.

According to these routines, the robot may conduct an effective methodof human-robot interaction. Most fundamental motion behaviors areasynchronous (or independent of) the dialogues. Behaviors such as escapeor safety reactions to events are not affected by the dialogue. Thecommunication script segments (queries, choices, replies) are receivedby the robot from its internal database or a remote database, andinclude the dialogue branches with robot speech prompt text (such asdialogue queries, replies, and confirmation/feedback responses) as wellas human response text (such as the choices for the person to repeat orselect). The robot interprets the communication script segment togenerate an audible robot speech prompt, either by referring torecordings; by consulting a speech synthesis phoneme script that goeswith the text; or by having on-the-fly text-to-speech synthesis (each ofthese being capable of including script or timestamp synchronized visemetags defining facial animations, earcons defining emphasis sounds, or“animotion” scripts defining robot emphasis motions). Animotion scriptstend to define a desired expression during the communication scriptsegment by adding an expression motion, usually one or both of a headmovement sequence including nod axis head movement or turn axis headmovement, or a robot movement sequence including movement of the entirerobot.

The robot receives input in the form of either recorded speech from theperson via its microphone array, or the result of a push-button ortouch-screen identification of the selected response choice. If at anypoint during this dialogue, the robot detects an event that requires aresponse from the behavioral system (e.g., in moving into an expressionmotion, the robot bumps a table or other obstacle, or has moved partwaytoward a second person), the robot interrupts the dialogue branch inresponse to the event detected by one of the plurality of behaviors(i.e., via the sensors used by those behaviors) to execute anasynchronous response (such as stopping the robot). After anyappropriate asynchronous response (including a further comment from therobot regarding the change its motion or pose, or what was discoveredthat caused the change and asynchronous response), the robot recoversthe dialogue branch after the execution of the asynchronous response.The robot interrupts expression motion(s) in response to the eventdetected by the robot. The robot is stopped (or other correctivebehavior) to reposition the robot according to the event.

FIG. 7B depicts a dialog routine constructed using the generic routineof FIG. 7A. At Step SD1′, the robot begins a greeting sequence,triggered when the resident returns to the home at a time that the robotrecognizes as the conclusion of the workday. The robot welcomes theresident home at Step SD2′, then asks about the resident's day at StepSD3′. In this case, for example, the robot may combine the question ofSD3′ with a display on it's input screen of the question and potentialresponses (in this case, “Great,” “OK,” “Terrible,” or “I'm in a rush”).A number of robot replies are depicted at Step SD5′, or the robot mayend the dialogue if the resident has no time or interest to interactwith the robot. At Step SD6′, the robot may begin a number of otherinteraction sequences, such as asking the resident about the day's or afuture day's work, remind them of scheduled events, advise them on theimportance of getting a good night's sleep, etc. As indicated,interactions may lead to other interactions, questions, etc. Theseinteractions may continue indefinitely, until the robot reaches an endpoint, until the resident requests termination of the interaction, etc.

FIG. 7C depicts a bump interaction algorithm SD10 constructed using thegeneric algorithm of FIG. 7A. At Step SD11, the robot begins a bumpsequence, triggered when the robot bumps unexpectedly into an object.The robot makes a bump sound at Step SD12, such as a beep, crash, orother sound to signal contact with an object. The robot then initiates abump analysis sequence SD13, to determine the frequency of the sensorevents (in this case, contact with the object). For example, the robotmay contact an object a single time, as in Step SD13 a, or several timesin a predefined period, as in Steps SD13 b and/or SD13 c. The decisionmaking as to the expressions, SD 14, that the robot uses depend on thesensor events, but need not effect the behavioral response of themobility response. In other words, the robot may output any expression,sound, affect, etc., but these are independent from the robot'sbehavioral mobility system (e.g., the robot may back up, if required,while expressing frustration). In addition to outputting an audible (viaits speaker) or visible (via its display) expression, SD14 a, the robotmay also utilize other animations or sounds, SD14 b. By utilizing itsmapping function, the robot may also determine if it has hit an objectat other times in the past in this particular location, Step SD15, andthus learn to avoid areas where it has experienced mobility problems.The POP step allows the robot to exit the bump interaction sequence.Similar to the dialog algorithm of FIG. 7B, this bump interaction maylead to other interactions, cause pleas or questions directed to anearby resident, etc. These interactions may continue indefinitely,until the robot reaches an end point, until the resident offersassistance to the robot, etc.

FIG. 7D depicts a routine for the robot to present a question to theresident, with a limited number of responses (five or less, usuallythree), and in which most of these responses are confined to simpleaffirmative, negative replies. At step 7D-10, the robot retrieves orreceives a script segment from its own database or a remote database.the robot may carry all dialogues or common dialogues on board, butother embodiments may also retrieve dialogues from a remote server, onan ad-hoc basis (as a rarely encountered dialogue tree is explored) oron a predictive basis (retrieving or some all possible branches in adialogue tree ahead of the speed at which the resident is moving throughthem), or as part of a scheduled or on-demand update procedure. Asexplained above, the robot then “speaks” an audible query or question(step 7D-12 and shown at 7D-2, from recording, phonemes, or text) and atthe same time displays the corresponding question in text (using ascreen as shown at 7D-1, optionally highlighting each word of the querysentence as it is pronounced or the query sentence all at one time) aswell as the answers the robot expects to hear as subsequent branches inthe scripted dialogue tree.

Subsequently (step 7D-16), the robot attempts to receive an audibleresponse and process it. FIG. 7D does not show processes for robotbehavior in the event that no response is detected at all (e.g., theresident has walked away, the resident for some reason does not to speakat all), but such processes would be compatible with this routine. Inaddition, should the person reach across and press a button ortouchscreen beside the displayed choice as a way of answering thequestion, the process of FIG. 7D would move immediately to step 7D-22noted below (confirmation repeat of the selected choice). The processingin this case is speech recognition, but the set of potential responsesis limited to those shown on the screen (one exception is theaffirmative, negative response, which may have a larger set ofpossibilities). The resident may choose to read the response text outloud from the screen; may have memorized the typical responses as aresult of frequent use, or may choose to input using touch screen orsoft buttons. As shown in the diagram, numbers may also be displayed(and recognized), but the robot would not necessarily explain on everyoccasion that a number may also be spoken and recognized. The choicesand thereby the processing is limited such that the speech recognitionmay be done on an embedded-class processor of less than 1000 MIPs,shared with all the remaining tasks and computation necessary forrobotic operation. If more speech recognition resources are available,they may be devoted to a higher success rate rather than a moreversatile recognition set.

As shown in FIG. 7D, the robot provides the resident with a designatednumber of “retries” (one shown) at steps 7D-18, 7D-20 if speech analyzedand processed is not recognized as one of the expected responses in thedialogue tree at step 7D-16. A retry message may be spoken (shown at7D-5) and the question itself or possible answers may be highlighted orblinked together or sequentially (7D-4) to attempt to refocus theresident's attention. If, on the other hand, the speech analyzed andprocessed in step 7D-16 is recognized, the robot may confirm this atstep 7D-22 with audible repeat-back feedback (shown at step 7D-7) and/orby highlighting or blinking the recognized answer at (shown at 7D-6).

In this manner, the received (from database) communication scriptsegment includes an output query sub-script text and a response tree offive or less sub-script response text candidates (often “yes”, “no”, andan alternative such as “I don't know”; on other occasions a list, e.g.,pill type “red diamond”, “green”, “white”, “none of the above”). Thelist is kept at five or less so as to (1) avoid overwhelming attention;(2) avoid overwhelming display screen “real estate,” (i.e., noscrolling, text large enough for easy review) and (3) limit theresources necessary for speech recognition. The output query text (i.e.,the questions asked) are related to or associated with an audible outputsignal (e.g., phoneme codes, compressed recorded audio), and output as aspoken query to a person. Both the output query sub-script text and thelimited number of responses are displayed together on a display of therobot. The robot receives, via a microphone or a vectoring or othermicrophone array, the person's spoken response as an audio input signal,which is processed to check/recognize if it corresponds to what has beendisplayed (i.e., all the responses expected to the question). If thesignal recorded by the microphone is recognized, the robot issues anoutput signal (i.e., a voice or text confirmation, highlight, orblinking) to feed back or repeat back the recognized response. If not,an output signal, also a voice or text reprompt, highlight, or blinkingprompts the user to retry communicating a response. In some cases, therobot can request confirmation from the resident by monitoring for aconfirmation of the correctness or incorrectness of the recognizedchoice.

In the event that audio reprompting is ineffective, the reprompt cantake the form of highlighting (including blinking or the like) thedisplayed sub-script text on the display of the robot, and at the sametime receiving the response choice via a manually operated control(e.g., soft button, touch screen) associated with the display. There issome advantage if two of the response text candidates are a simpleaffirmative and simple negative response, and if the processing thenchecks for speech corresponding to many different kinds—a family—ofaffirmative responses equivalent to the simple affirmative response(yes, yeah, uh-huh, sure, etc.) or includes speech corresponding to afamily of negative responses equivalent to the simple negative response(no, nope, nah, I don't think so, uh-uh, etc.). Other messages can becommon among many scripts (I don't know, please go back, etc.), and insuch cases, the robot may recognize a limited set of possible responsesthat are not shown on the screen (please go back, come back later, quit,etc., show me my schedule). If there is no yes or no answer, the list ofanswers may be limited to three or less to significantly limit speechrecognition work.

A standalone network adapter provides firewall circumvention andzero-configuration of network access for the robot, without requiring auser-interface for configuration. This may be done independent of therobot and, in certain embodiments, can potentially bridge multiplerobots in the home. In one embodiment, WiFi is an non-broadcast extendedservice set identifier (ESSID), with wired equivalentprivacy/WiFi-protected access (WEP/WPA) enabled by default and “locked”.The robot and network adapter may be paired at the factory withgenerated, unique security information. Additional pairing operationsperformed at a later time may require physical proximity or line ofsight between the robot and network adapter (as verified by pairingcable, by short range RF such as BlueTooth, ZigBee, Wireless USB, or byshort range IR.

The network adapter functions as a firewall and may be into outside anyexisting infrastructure. It also includes “Simple Traversal of UserDatagram Protocol (UDP) Through Network Address Translators (NATs),” asdefined, for example, in http://www.faqs.org/rfcs/rfc3489.html, thedisclosure of which is hereby incorporated by reference herein in itsentirety. This functionality may be embedded into the device, thusallowing the network adapter to act as an Internet gateway, grantingInternet-access to recognized robots in a home environment. There are anumber of ways to access the firewall circumvention features of networkadapter, for example, by the robot having a MAC address within a knownrange.

General enabling network architecture is shown in FIGS. 8A and 8B. Eachrobot 10 in a home (multiple robots or other embedded devices withaccess to the robot base station possible) is linked to the robot basestation via different levels of pre-installed security and compatiblecryptographic keys. As shown in FIG. 8B, the connection 8B-2 wouldgenerally be carried in frames or packets of an RF protocol, would useIP stack protocols within this (TCP, UDP, HTTP), and would have a trustboundary within this (a virtual private network VPN or secure socketlayer SSL boundary). Generally, the robots 10 are wirelessly connected,and the robot base station is an RF station using an RF bandwidth andprotocol sufficient for the data that will be sent to and from the robot20. For example, for a robot 10 capable of videoconferencing, arelatively high bandwidth RF modality such as 802.11a/b/g/n would beuseful. For a robot 10 which does not transmit video or audio data,Bluetooth, wireless USB, or proprietary networks could be used. The basestation can be configured to add encryption to the RF protocol (to limitaccess to the network), or without (to permit the highest speeds).Whether or not the RF protocol is itself encrypted, the innermost trustboundary encrypts and protects data that can be sniffed from the RFsignal; and robots and other authorized devices are on a media accesscontrol MAC connection-permitted whitelist, and/or are provided withappropriate public and private cryptographic keys for the VPN or SSLconnection. The base station 8A-6 may also provide general RF-protocolor WiFi network connectivity for other devices in the home; and therobot(s) (especially if provided with two transceivers) may act asrelays or repeaters to extend the range of the base station 8A-6.

The base station (in this view, 8A-6) is always connected via a modem ornetwork terminal (usually a cable modem, xDSL, or optical networkterminal) to a (usually broadband) Internet Service Provider (not shown)and then to the public internet (cloud). The robot base stationgenerally has the functionality of and provides a router (e.g., DHCPserver, NAT, firewall, etc.) so does not need to traverse a router.Nonetheless, as described herein, in some cases the robot base station8A-6 will be behind a firewall or NAT service, and some techniques formatchmaking are addressed herein.

The robot base station 8A-6 regularly or intermittently connects to amatchmaker 8A-10 (a web or database server), which maintains up to daterecords of the current IP address of the robot base station 89A-6(assumed to be, in most cases, dynamically assigned). Once a match ismade (i.e., a caregiver station 8A-4 and robot base station 8A-6 areinformed of each other's IP address), a secure peer-to-peer connection(as shown in FIG. 8B, connection 8B-8) is established The matchmaker8A-10 may not be necessary in an IPv6 regime with ubiquitous unique IPaddresses. As shown in the right side of FIG. 8B, the base station knowsthe address of the matchmaker or supernode, and connects 89B-4 viaprotocol layers similar to the robot-base station connection 8B-2,except that the outer layer in this case would be protocols appropriatefor whatever medium carries internet traffic from the base station tothe matchmaker (e.g., Ethernet, ATM, X.25, or other packet network). Thematchmaker 8A-10 or supernode informs the caregiver's station of the IPaddress of a matched robot or robots 10.

In addition, the matchmaker 8A-10 may be part of a network which reliesupon so-called supernodes to provide routing among privileged clients,or the matchmaking function may be handled by a network of nodes andsupernodes which do not have any access to the data network 8A-8, 8A-12,8A-14. For example, supernodes may be nodes with a public or fixed IPaddress, not behind a firewall. Cryptographic keys for user identity andpassword are stored on the matchmaker 8A-10 as a login server. Eachrobot base station or caregiver station may use a protocols similar toSTUN (rfc 3489) protocol and TURN protocols to determine what kind ofNAT or firewall intervenes. To initiate, the station may open (TCP orUDP) listening ports at a random port number and specific common portnumbers (80 for HTTP and 443 for HTTPS). Each station may maintain acache of supernodes or matchmakers and their IP addresses and knownrandom ports. Upon connecting to the internet, either station may sendpackets (TCP or UDP) to a supernode or matchmaker IP address at thehistoric port number, await a response, then try to connect on the HTTPport and then HTTPS port. After being connected to the supernode ormatchmaker, this matchmaker or another matchmaker, Web server orsecurity server may authenticate the station. The supernode ormatchmaker may also exchange sufficient packets to inform the station ofthe IP address of a different matchmaker or the address of a particularlogin authority that can authenticate that station. During a connection,each station may populate its cache with supernodes, nodes, matchmakersand their last known (random) open ports and IP addresses. Any node(robot base station, caregiver station) or supernode may act as a routerto forward and route traffic between a matched robot base station orcaregiver station if either or both are behind port-restricted networkfirewalls or NAT. This is typically similar the “Skype” peer to peertelephony network, and would be capable of interoperating with such anetwork. In the present arrangement, preferably, idle caregiver stations(typically ordinary PCs running authorization software, VPN, and/orclient software) act as routers in such cases, as this would tend not toburden the supernodes, and also would avoid using robot base stationnodes which would typically have less processing capability (i.e., aboutthe same as a consumer router).

As shown in FIG. 8C, using this or a modified system, authorized devicessuch as robots or pre-authorized devices such as a VoIP phone or mediastation (i.e., that have cryptographic or unique identity informationknown to the robot base station, such as a MAC address, public key,signature, or that can transmit this information locally over a directwire connection, scannable ID, serial connection, and the like) can bepermitted by the robot base station to immediately participate in atleast part of the trusted network(s). The base station will permit anauthorized device trying to become an identified node to listen on arandom port nn, which will notify the matchmaker that the device isavailable at that port (i.e., including the IP address assigned to therobot base station, the port that is being listened upon, and identityand/or security information associated with the robot or pre-authorizeddevice). In other cases, no identity information is necessary, as eachdevice accessing via a base station will have a different random port.The matchmaker and robot/device will then conduct challenge-response(including security, authorization information) to authenticate therobot/device at the matchmaker. If an unauthorized device tries to usethe base station, the device may become authenticated by negotiating itsauthorization via the base station and a list of authentication servers(e.g., registering by sending a signed and/or pre-authorized privilegecode, already known to the authentication servers, via the basestation). Thereafter, the device or robot may be authorized at that basestation. The same process may take place at a caregiver station, exceptthat a caregiver station would immediately attempt to connect to asupernode or matchmaker. In addition, the random port strategy may besupplemented by using an HTTP port, HTTPS port, and/or intervening nodepacket forwarding and routing when either the robot base station orcaregiver station are behind a firewall, closed ports, and/or NAT.

The base station 8A-6 is also connected to a Web server or server 8A-8which hosts various applications useful on the robot 10. The Web server8A-8 has access to a file system 8A-12 with content to be used by therobot 10 (e.g., multimedia content); and also to a generalize database.The database may store user profiles for the residents, the dialoguesavailable for robots 10 to use, schedules and the like. Any dataconsidered confidential or sensitive can be obscured as to identity orcontent by cryptographic keys. Data may be used or processed by thedatabase in a manner that the database owner (not the resident) may notinspect or attach an identity to private date. Join tables can matchrecords stored on the robot or base station with data stored by thecaregiver, so that data collected or sent from either while the other isnot on-line to connect peer-to-peer 8B-8 may be associated. Datanormally preserved only on the robot or by the caregiver or caregiver'snetwork (confidential medical history and records, etc. may bemaintained on the database 8A-14, but preferably in an encrypted backupform that is recoverable only by one of the caregiver, robot, or robotbase station or a proxy (e.g., the resident's home PC).

In this manner, a robot system, includes both the base station 8A-6 androbot 10. The base station includes a wireless transceiver capable ofcommunicating TCP/IP transmissions over a local wireless protocol and awired Ethernet connector for communicating TCP/IP transmissions over alocal wired Ethernet accessing the Internet. The access point circuit(e.g., in the robot base station) transfers TCP/IP transmissions betweenthe local wired Ethernet and local wireless protocol, and is limited toa predetermined IP address assigned to and locked to the robot (e.g.,cannot be changed by a resident or caregiver without authorization, orat all), predetermined shell level encryption locked to the robot (suchas the discussed VPN and/or SSL), and predetermined ports to theInternet open only to the robot, (e.g., one random port assigned to eachrobot and opened, or under the same language, a common port such as HTTPor HTTPS in combination with an intervening random routing node). Therobot itself would include a wireless transceiver capable ofcommunicating TCP/IP transmissions over the local RF or wirelessprotocol and a client circuit (e.g., CPU and OS with IP protocol stack)for transferring TCP/IP transmissions over the local wireless protocol.

Preferably, the robot base station includes a plurality of antennas (therobot may also), and makes use of 802.11n multiple-in, multiple-outantenna diversity and selection to overcome issues of multipathpropagation within the home, not limited to 2.4 GHz unlicensedfrequencies, but in bands from e.g., 900 MHz up to around 10 GHz.Further preferably, the robot base station further encodes wirelesstransmissions using orthogonal frequency division multiplexing. In sucha case, the robot base station may be portable and incorporate elementsof the caregiver station (such as a screen capable of relaying cameraand video information for teleoperation, and a controller forteleoperating the robot), and the embodiments contemplate that theplatform for the robot may be treaded and skid steered, withsurveillance cameras on board. Video is transmitted from the robot tothe base station at the highest possible speed, multipath resistance,and frame rate using multiple-in, multiple-out antenna diversity,orthogonal frequency division multiplexing, IP or IP-compatible packetprotocols that do not error correct (like UDP), and optionallypredictive wavelet based video compression like H.264 AVC or MPEG 4.

In the embodiment depicted in FIG. 8, the robot authenticates via achallenge-and-response exchanging with an upstream server. The networkadapter opens a small hole to a known authentication site forunrecognized robots in the home. This authentication site issues achallenge to an unrecognized robot. If robot responds with acryptographically correct response, an authentication token is sent tothe network adapter, which stores the token and allows access from thatpoint to the Internet. In still another embodiment, the robot is granteda random port number to listen to, and this information is alsoforwarded to the matchmaking service.

A central service may provide a matchmaking similar to dynamic DNSservices, but for commercially available robots that utilize theparticular network adapters. Under these circumstances, each robot wouldbe shipped to a consumer with a unique pass code to map the owner to thedevice when the owner first connects to the matchmaker service. In thiscase, the matchmaker service is web-hosted centralized user interfacefor robots. Service proxies configuration and user interfaces betweenrobots and users, who are both Internet clients. Additionally, thematchmaker service may operate as a fleet management tool (for softwareupdates) and a portal for the robots in a particular home. From thiscentral site, a user can “connect” to a robot, which redirects the userto the user interface hosted on the robot.

FIG. 9A illustrates a reporting routine which may be implemented by amobile robot in situations where safety concerns require transmission ofinformation to a remote terminal (a base station, caregiver computer,etc.). At step S1, the robot retrieves reporting instructions from acomputer network—for example, by downloading a list of information thata remote caregiver wants to receive from the mobile robot. Suchinformation may include, among other things, what time is the robot lastdetected the presence of the resident, whether issuance of medication tothe resident succeeded, etc. At step S2, the robot may collect suchinformation. The robot then checks the current time and compares it tothe schedule at step S3; and, if it determines that the scheduled timehas come to transmit information, at S4, the robot may transmit theinformation to the remote terminal at step S5. Otherwise, the controlmay return to step S2, for example.

In response to schedules or events throughout the day, the mobile robotgenerates updates including updated information regarding the resident,including but not limited to: (a) medication compliance information; (b)presence or absence of the resident, recognized by patterns of sound orother detections; (c) status or “nothing unusual” reports; (d) reportsof visitors; (e) updates entered by the resident as to their plannedschedule (“I'll be out for two hours”); (f) report of unusual patternsof sound (distress noises, calling out noises) or unusually loud sounds;(g) requests for communication from the caregiver or other familymembers to the resident. These updates include event-responsive updates,data-change updates, status updates, and scheduled updates.

The robot uploads the update information to the computer server, whichis integrated with or in communication with a push server, using a pushupdating system. The push server, similar to a mail delivery agent,sends (or pushes) newly received updates to the update client, similarto a mail user agent. Both the robot and caregiver's terminal may be anupdate client. The push server monitors the network of robots andcaregiver clients, and when it sees a new update for a caregiver, itretrieves the update and pushes it to the caregiver's terminal.Similarly, when the push server sees a new update for a robot, it pushesthe message to the robot. The updates may or may not be separatelymaintained and archived.

As shown in FIG. 9B, a push server P provided on the internet Icommunicates with the mobile robot R (via the base station B) and thecaregiver's terminal C in such a way that reports and updates from therobot (which are reported to the push server in client mode by a clientrobot) are pushed to the caregiver's terminal C. The caregiver'sterminal C may be a telephone, messaging device (blackberry or otherpersonal digital assistant), or computer browser or other client. Inthis context, information being delivered from a push server P to aclient device is based upon a predefined set of request parametersoutlined by the client device. This can be delayed or in an instantmessaging fashion. The push server P pushes content to the caregiver'sterminal C, without the caregiver's terminal C polling or otherwiserequesting updates from the push server P. As a result, the informationupdated by the mobile robot R is relayed to the caregiver's terminal Cvia the push server P on the Internet I. The push server P may pushupdates as well as e-mail. Alternatively, pull technology such as RSSmay be used for delivery of robot-originating content. In such a case,the caregiver's terminal C may automatically retrieve any updatedinformation from the computer server, for example, at particularintervals during the day.

The robot of the present invention provides a rich interactiveexperience for a user by utilizing visual cues to indicate its responsesto certain events. Those cues include, at least, image displays on oneor more of the screens and head or other physical movements to conveyreactions. FIG. 10A depicts a number of exemplary affect expressions tobe displayed on a screen 26 of a mobile robot. Although the affectimages depicted in FIG. 10A are shown on the display 26 of head 16 of arobot, affect images could also be displayed on a body-mounted screen.Optionally, the affect images may only utilize a portion of a displayscreen, leaving the remainder open for other interactions and/orfunctions.

As displayed, mouth, eye, and eyebrow objects (such as those exemplaryexpressions depicted in FIG. 10A) can be arbitrarily formed from amultiplicity of pixels using a matrix display, or can be formed in setshapes from a number of segments using a segment display. Of course, adisplay may incorporate both segments and matrix portions, and matrixpixels may be considered one kind of segment. The segment or facialmatrix display may be provided with a sufficient number of segments orpixels by conventional manufacturing techniques.

The following discussion describes either a segment panel or matrixpanel, with distinctions noted at appropriate portions. In discussingthe matrix panel, terminology used to create animations in Macromedia™Flash™, a portable animation system, is useful. In this terminology, a“movie” may be a collection of scenes, which is a collection of objectssuch as text objects and image objects, which in one embodiment may beplaced in layers onto a background. The movie and objects are responsiveto events, and may apply effects (animations that change the appearanceof an object) as well as carry out actions outside the movie. Indiscussing the operation of a segment panel, an object may be a singlesegment or group of segments that may be turned on or off in sequence orseparately, which can give the impression of motion or a change inappearance. In both cases, “objects” may be animated and accommodatetransitional animation states. Notwithstanding the use of thisterminology, the invention is not limited to the discussed animationsystems.

The display 26 implements an eyes-nose-mouth display which is animatedin sync with speech and interaction to express the changing affect andnon-verbal behavior of the robot. The animated expression of the displayis controlled subject to a number of variables within the system:non-verbal behavior synchronized with speech, phoneme animationsynchronized with speech, base expression from dialogue and affectmodule, and several specialty expressive sequences. The functionalelements of the expression include several base expressions, several eyegaze directions, several eyebrow positions for emphasis gestures, andseveral mouth shapes (visemes) for phoneme animation. These elements areindependent (orthogonal), i.e., phoneme animation, gaze shifting andeyebrow raising work regardless of the base expression, which includeSad (mild), Concerned, Neutral (positive), Happy (with at least 4gradations from contentment to joy), Surprise (with differentpresentation for positive and negative surprise), etc. There are“in-between” states (“tweens”) in all these elements, for smoothinganimated transitions from state to state.

Eye gaze direction may provide, for example, 16 different positions ofdirect gaze from right to left. Additionally provided may be twopositions upward-left and upward-right, and two positions downward-leftand downward-right. Reflection-indicators on the eyes may be omitted,set depending on directionality of room illumination, or kept stable. Atleast three eyebrow positions may be provided—neutral, raised medium,raised high, plus tweens. Eyebrows participate in forming baseexpressions as well.

Phoneme animation utilizes a subset of 13 visemes (a “viseme” is set ofanimation frame frames of a mouth in positions corresponding to speechsynthesis phonemes, according to the timing and pace of human mouthmotions used to form such phonemes; an “earcon” is the audibleequivalent of an icon, i.e., a short, meaningful sound that conveys anidea, object, or action without the use of spoken language), tweened fortarget speech rate of 5 phonemes per second. Expressions that indicate atongue may be eliminated to reduce this subset. A set of closed, A, B,E, F, K, O, OO R, TH comprises a basic set of phonemes. A larger set mayinclude any or all of Silence; P, B, M; W, UW; R; F, V; TH, DH; L; S, Z,D, T, N; SH, CH, JH, ZH; Y, IY, IH, IX, AW, H, K, G, NG; EY, EH, UH; AE,AX, AH, AA, AO, ER, AY; OY; and OW.

Specialty expressions may include Wink, Blink, Curious, Inquisitive(e.g., one flat eyebrow with sideways glance), Dilated pupils, Laughing,Crying, Sleepy (used when the robot battery level becomes low), Thinking(used while downloading something, might include brow furrowing). Theexpressions depicted in FIG. 10A may be utilized in conjunction with thevarious head orientations, if desired.

FIG. 10B depicts expression motion actions and positions for the robot10. The potential default position of the head 16 (shown in FIG. 1A, butnot shown in FIG. 10B) may be regarding the resident.

As generally depicted herein. the form of the head and torso of therobot may be designed to provide shrugging, nodding, head shaking,looking away (change of subject) and other gestural cues; the mobilitysystem permits approach and recede motions (personal space andconversational attention cues). It is important to note that it is notnecessary that the robot have a head, or indeed any human or animalattributes. For those known gestural cues that involve motion of aperson's head, shoulders, or the like, an analogous motion usingportions of the robot that are in similar positions, and/or of similarprofile, and/or are exaggerated using the entire body of the robot, ifarranged according to the same or similar conversational timing and cuesas human gestural cues. Some of these are shown in FIG. 10B. Theapproach and recede motions may also include looking away and othergestural cues. In general, as discussed herein, motion to provide agestural cue is included in the term expression motion, and can betriggered by script, asynchronously, or periodically. As shown in FIG.10B, the robot may approach to the correct distance for a particularculture or person (which may be recorded and adapted over time as, e.g.,the robot is able to detect that conversations with the residentcontinually involve the resident edging away from the robot). This is anexample of a gestural cue, another typical gestural cue would beslightly turning the entire robot or robot's head away from the residentmomentarily at a change in subject in the conversation. As also shown inFIG. 10B, the robot may perform “politely and graciously,” moving out ofthe way of the resident if it becomes apparent the resident is beginningto move in a certain direction—the robot's recording of the position ofdoors and/or traffic paths and/or household obstacles would facilitatekeeping out of the way. This is an example of the robot simulatingsocial interaction via robot expression motion. As also shown in FIG.10B, the robot may perform “animotions”, i.e., entire-robot (via thewheels) movement scripts designed to convey expression (these may alsoinclude movement of other parts of the robot and/or sound, etc.). Eachof these kinds of expression motion is considered part of the expressionmotion and/or asynchronous robot motions and asynchronous eventsdiscussed herein.

In accordance with an embodiment of the present invention, a mobilerobot may provide interaction with a resident to promote or insurecompliance with various tasks or activities. For example, the mobilerobot may provide reminders and other stimuli for numerous scheduledevents, as illustrated in FIG. 11A. This would be particularly usefulfor interacting with an elderly or other resident who may havedifficulty remembering to take medications at the appropriate timesduring the day. In addition to supporting medication regimens, the robotmay support dietary regimens, may provide recurring recommendations formanaging a chronic medical condition (stretching, drinking water,resting, etc.), and instructions for restorative therapy(therapist-recommended exercises, etc.). A schedule 50 stored in therobot's processor may be set by the resident or a remote operator orcaregiver. For example, the resident may enter events as desired, eithervia a computer or personal digital assistant, or directly by utilizingthe robot's interface abilities. Additionally, the resident may requestthat certain behaviors be performed immediately. Similarly, a robotschedule 50 also may be linked to a doctor's computer or personaldigital assistant to record critical appointments, medicinal doses, etc.Additionally or alternatively, the schedule 50 may receive instructionsfrom a pharmacist's office when a new medicine is prescribed, forexample.

As shown in the schedule 50 in FIG. 11A, a medication compliance routine54 may be scheduled following a morning regimen 52, which may includethe robot waking the resident, a pill-loading sequence, a stretchingregimen, a vital signs check, etc. The morning behavior may also be usedto remind the resident of any of the activities that are scheduled forlater that day, or even for particular appointments for future dates. Byincreasing the resident's cognitive and physical involvement in dailyactivities (such as planning one's own daily schedule and/or loadingmedication), the robot increases the resident's involvement in,responsibility for, and control of their own regimens. Such involvementin one's own care may be beneficial.

Additional regimens may be supported by the mobile robot, with similarreminder schemes. For example, the robot may provide the resident withreminders for social visits 56, or entertainment events 58 previouslyplaced in its schedule 50. During the medication compliance routine 54,the robot may remind the resident of the purpose of the interaction,note the amount of medicine that must be taken, and request permissionto proceed with the compliance routine. In the present example, themobile robot may, depending on whether the robot includes a medicinedispenser, magazine, or carrier, (i) direct the resident to go to theroom in which medication is kept, (ii) offer medication from an cup orcups borne by the robot, along with water, and/or (iii) open anappropriate portion of a pill dispenser, in order for the resident toretrieve and take the medication. Accordingly, by simply reminding theresident that the time for regimen compliance has come, the probabilityof regimen compliance is increased. However, various actions can betaken by the robot to further increase this probability. For example,the robot may be provided with an associated medication cache, carrier,magazine, or dispenser, and may also include with a water carrier ordispenser. When the compliance routine 54 is initiated by a time orother event trigger (for example, after a meal, upon direction from aremote caregiver, etc.), the robot may take the medication to theresident or bring the resident to the medication.

FIG. 11B illustrates an exemplary regimen initiation routine, I, themobile robot may follow for beginning regimen routines. At step SI1, themobile robot checks the current time (or notes the occurrence of theevent), and compares it to schedule 50 (FIG. 6A). If at step SI2 therobot determines that it is time for a medication routine or otherregimen routine to begin, the robot proceeds to find the resident atstep SI3 (otherwise, the control process may loop back to step SI1).Finding routines are described below. At step SI4, the mobile robot mayquery the resident, and then determine, at step SI5, whether permissionhas been granted for an interaction. If so, then the mobile robotperforms the interaction behavior at step SI6; otherwise, at step SI7,the robot checks the permissions that have been granted to determinewhether the robot may contact the remote caregiver regarding refusal.Alternatively, if the regimen is non-critical (e.g., a social orentertainment event), the robot may move to step SI10 and leave thearea. If at step SI8 the mobile robot determines that it is permissibleto inform the caregiver of the resident's refusal to interact with therobot, it then proceeds at step SI9 to transmit notice to the caregiver.Otherwise, if permission was not granted, and assuming that no overridecondition exists, the robot may leave the area at step SI10.

An exemplary regimen compliance routine, C, is depicted in FIG. 11C. Therobot's display screen(s) or speakers may provide displayable or audibleinstructions or description of how a medication should be taken or otherregimen performed. When the schedule 50 indicates a regimen complianceroutine (e.g., a morning routine 52, a medication compliance routine 54,a social visit 56, an entertainment event 58) is scheduled, the robotmay then help the resident understand how and why the regimen is to befollowed, as depicted in SC1. For example, the robot may explain thepersonal medication dosage information, which may include the medicationthat the person is to take, and the schedule they are to take it on,whether that is based upon time, events, or other factors The robot thensets an compliance counter to Step=0, at SC2, to track compliance duringthe routine, then gives the first reminder to follow the regimen, atSC3. If the reminder is not initially refused, SC4, the robot assists asrequired, SC5, by providing pills, guiding the person to a locationwhere the pills are stored, displaying and/or verbalizing exerciseinstructions, preparing a videoconference connection, etc. After a settime or event, the robot confirms compliance, SC6, either with aquestion or other compliance-confirming action (e.g., checking contentsof pill dispenser), and, if compliance is confirmed, SC7, the routineterminates, and the robot returns to monitoring the schedule 50 (FIG.11A). If compliance has not been confirmed, the robot increases thecompliance counter by 1, SC7′, then determines if the routine iscritical, SC9. This step SC9 is also reached if compliance with theroutine is initially refused at SC4, after an increase of the compliancecounter by S+1 at step SC8.

To increase probability of compliance, the robot may include a “snooze”function, SC9′, that permits the resident to temporarily delay themedication or regimen when the regimen is non-critical. The snoozeroutine may be limited in recurrences for particular regimens deemedmore important, but not critical, by the resident, caregiver, or robot(e.g., medication compliance, therapeutic compliance, etc.). For lesscritical regimens (e.g., social and entertainment events, morningwake-ups on days with no events scheduled, etc.) the snooze routine maytime out entirely. The snooze routine may also be modifiable with asecondary reminder (e.g., when permitting a delay by, for example, 15minutes, the robot may issue a reminder that the compliance with theregimen will be soon required), and then return to SC3. The snoozefunction SC9′ may also be utilized when circumstances for compliance areunfavorable (e.g., the person is preparing a meal when a teleconferenceis scheduled, etc.). When a regimen compliance routine is interrupted ordelayed by necessity and by the resident's control, it may be reinstatedafter a requested delay. Such delays may be managed by postponementrules that provide guidelines as to how many times and how longmedication may be delayed or refused, and whether and how a caregiver isto be notified upon a delay or refusal.

If the routine is critical, the robot determines if the compliancecounter has met a predetermined threshold, SC10, if not, the robotrepeats the initial reminder at SC3. In the event the threshold isexceeded (resulting from persistent refusal by the resident), the robotis provided with more assertive reminders, SC11, allowing the robot toutilize other speech (“Bob, it is very important that you take thismedicine”), or affect responses (Angry, Sad) to convince the resident tocomply with the regimen. If the increased assertiveness reminder is notrefused, SC12, the robot moves through the assistance subroutine,including steps SC13, SC14, SC15, and SC15′ (similar to the assistancesubroutine beginning with step SC5 above) as needed. Continued refusalSC12 increases the compliance counter, SC16, until a second threshold isreached, at step SC17. As an additional compliance step, the robot mayreport continued refusal to the caregiver, with or without theresident's permission, depending on the application, SC18. Again,regimens deemed critical may be reported to the caregiver withoutresident permission, less critical regimens may require the resident'spermission, or may go entirely unreported. Additionally, at thecaregiver's or resident's discretion, the report to the caregiver mayprovide an opportunity to exercise caregiver intervention, e.g.,including a videoconferencing call, where the caregiver may encouragethe resident to follow the regimen. Alternatively, for caregiverswithout access to a videoconference system, the display of the robot mayact as an avatar for the caregiver, wherein speech received from thecaregiver is converted into viseme (and, optionally, phoneme) sequenceson the display of the robot, to communicate with the resident andconvince compliance.

The robot is also able to take other action in the event it isdeliberately or inadvertently ignored, so that probability of compliancemay be increased. Reasons for non-compliance can include simple orcondition-dependent forgetfulness about what actions to take, or howthose actions should be taken. Moreover, unavailability of medication atthe designated time, other time or scheduling problems, the resident'sinability to comply because of a medical condition, lack ofunderstanding of the necessity of following the complete complianceregimen, and dislike of side effects or other disincentives may impactcompliance. The robot may provide an option to call the caregiver toprovide assistance when a compliance regimen is not followed or if otherproblems exist or arise at any point during the sequence. The caregivermay also remotely interrupt or conclude the performance of anyinteraction.

The camera and microphone on the mobile robot also allows the robot tooperate as a video/teleconference station. As a videoconference station,the display may function as an avatar for the other party (as describedabove with regard to the caregiver avatar), or the robot may include avideo coprocessor capable of processing high-compression video such asMPEG-4, H.264 or AVC, or other video and sound files. FIG. 12 depicts ageneral conference request routine, V, that may be utilized in oneembodiment of the present invention. For an outgoing conference, i.e.,one initiated by the resident, permissions to provide outgoing video maybe provided at the call initiation sequence. For incoming calls,however, permissions may be desirable to ensure that a caller may notview the resident unless the resident so desires.

The mobile robot may receive a conferencing request at step SV1 (forexample, over a computer network using a wireless networking protocol,such as any standard IEEE 801.11 or 802.15, or BlueTooth, UWB or otherimpulse radio). The robot would then proceed to find or locate theresident at step SV2. Navigation sequences for resident searching and/orlocating are described in more detail below. When the mobile robot findsthe resident, it may issue an audible and/or visible query at step SV3,for example, “Shall I accept this conferencing request?”. At step SV4,the mobile robot may monitor the microphone, camera 28, and/or othersensors for verbal, gestural, or other responses from the resident.Additionally, the resident may touch an “Accept” button on one of therobot's screens, press a button on the surface of the robot, or touch aparticular sensor. At step SV5, the robot determines from any one ormore of the above events whether compliance was granted to begin theconferencing session. If permission was granted, the mobile robot maybegin the conferencing session at step SV6; otherwise, the mobile robotmay proceed to decline the session (and possibly, send notice of thedecline to the remote conferencing requester) at step SV7.

To function as a useful companion to a resident, a robot may be able tonavigate within an unpredictable home environment. FIG. 13A depicts atypical home layout or floorplan, but the robot would not necessarilyrequire a spatial or blueprint “map” In an embodiment, the robot andcaregiver or resident, via a web-browser or the robot's own screen,creates an icon set (map) including only conceptual icons representativeof accessible rooms of interest in the home.

In constructing a topological map of the environment, the robot may moveabout the home and note rooms or other subdivisions of the environment.These subdivisions may be any logical division of a space, e.g., ahallway, quadrants or other portions of a large space, etc. The robotmay identify the spaces at boundaries of rooms via “lighthouses,” or byvisual identification of features (windows, etc.). Such space boundaryidentifiers are described in U.S. Provisional Patent Application Ser.No. 60/741,442, the disclosure of which is hereby incorporated byreference herein in its entirety. Additionally, the robot may recognizefiducials in the room, such as indicia projected onto the ceiling,self-similar tags, etc. Examples of fiducials that are projected onto aceiling are described in U.S. patent application Ser. No. 11/176,048,the disclosure of which is hereby incorporated by reference herein inits entirety. The robot may also utilize position information, such asprovided by odometry, optical or RF time of flight or angle of arrivaltriangulation or trilateralizing, or may use spatial estimates, e.g.,room-size detection, size of largest diagonal, etc., to identify rooms.As the robot explores the various rooms/spaces within an environment, itmay build a topological map to capture room adjacency information andmaintain this information during normal operation. This map informationis cached in the user/resident interface, or may be stored at an onlinesite. The robot may also identify persons and things (a chargingstation, doors, windows, keys, pets, etc.), optionally by recognizing aradio frequency (RF) tag carried on, present on, or worn by the personor thing. Additionally, the robot could identify a person by a signatureheat, voice, and/or visual recognition pattern, as described herein.

Once the robot completes, or as the robot completes, all or a portion ofthe topology (and resident/entity information), it may keep thisinformation local or send this information to a web server, aspreviously discussed, (or serves the content itself). Discussed hereinare methods for building an interface, an icon map, and meaningfulconnections between the map and the home, as well as methods for robotnavigation using the combination of icons and room identity information.A web client may render an icon map of the home, which may in someembodiments appear as a collection of rooms arranged by distance on thetopological map, not real-world distance. The web client may also drawand label figures or other markers for the resident or other entitieswithin the house. Thus, the location of any identified person or thingwithin the house may be tracked. Such technology allows the resident orcaregiver to monitor the location of objects, persons, or the likewithin the home, if these objects or persons are detectable to the robot(via tags or sufficient recognition resources). The resident or otheruser may rename or classify rooms: “this is a bathroom,” “this is mybedroom,” etc.

The location and identity of each of these rooms and entities may bestored within the robot memory or local or remote database, andpresented to the resident upon request, for example, on a robot displayor a remote caregiver station or web client. The robot may display abasic list of rooms and identified persons, things, etc., but preferablyarranges the icon map as discussed herein. If desired, the resident maytouch any room indicated on the screen to direct the robot to go to thatroom. As discussed herein, a privacy mode may require that the camerasof the robot are inaccessible to a remote caregiver when the robot isautonomously navigating from room to room, and require one-time ortrust-level permission of the resident to be activated once the robotarrives in a room of interest. Once in an identified room (ifpermissions are appropriate), the robot may take a video or still imageof the space, and either return to the resident to display this data, orsend it remotely to the resident's computer, networked television, orpersonal digital assistant. The robot may also be used as a find tool,for keys or remote controls or the like. If equipped with suitableobject recognition capability (e.g., scale invariant feature transformbased object recognition and appropriate learning and databaseroutines), the robot may maintain a list of people or things that it iscurrently tracking within the environment (e.g., according to where theywere observed last). By selecting one of those items, the resident maydirect the robot to proceed to the location where the particular personor thing is located.

FIGS. 21A, 21B and 22A-22C show a method for handling navigationcommands for remotely controlling a robot. Pursuant to this method, alocal user (such as the resident, a caregiver working the robot in theresidents home, or a setup technician) may construct a simple icon-mapof the users home to be used for room-to-room navigation. Althoughseveral steps discussed herein discuss topological adjacency and/orexploring the household, the basic method does not require topologicaldata, or exploration to build or understand topological adjacency. Thatis, if the robot can identify the room identity of the present room andbe directed to move to a room of another identifiable room identity, therobot does not strictly need a topological map, but may explore usingthe most direct room-to-room navigation it is capable of in order tofind the room it is seeking. Although a user may identify topologicaladjacency of known rooms, it is preferable that either the robot buildany adjacency matrix or that none be necessary.

As shown in FIG. 21A, at step TM2, the robot explores the household.This step is non-sequential and can be carried out later in the process.In this context, the robot may simply travel randomly or upon a directedpath from room to room, but a preferred mode is for the robot to beguided from room to room, following the resident or caregiver into thoseareas that the robot is to work in. At the same time, the robot may betold preferable places to sit and wait, what kind of room each room is,etc. However, because the method may also be carried out remotely, thisexploration may include tele-operating or web-driving (as disclosed inU.S. Pat. Nos. 6,535,793 and 6,845,297) the robot among all accessiblerooms. The robot may then have a count of accessible rooms (which may becorrected by a person, or an excessive number consolidated into fewerrooms, or the like). In the present examples, hallways are notconsidered rooms from the operator's perspective and are not assigned anicon (primarily because a robot parked in a hallway is an obstacle).However, hallways may also be treated as rooms.

At step TM4, the robot captures topological adjacency of differentrooms, and docks and chargers. Docks may charge and/or provide a dataconnection (e.g., such as a robot base station); chargers are intendedto recharge the robot but may also have data access. “Capture” in thissense may include taking the entry of data from a person or floorplananalysis, but generally means closing (topological) paths and loopsaccording to odometry or localization data, by routine or with theassistance of a person. At step TM 6, nodes are assigned by the robot.Simplicity means fewer nodes, e.g., one per room. However, bases andchargers may also have a node each, and hallways typically have a nodewhether or not they appear on an icon map. In addition, as shown in stepTM6, doorways and interesting positions (e.g., facing to the TV, behindthe chair, out of the way by the window) may also be assigned nodes. Atstep TM8, the number of rooms (e.g., the number of rooms a resident orcaregiver has entered into the robot as existing in the house) arecompared to the number of room identities (e.g., the number of roomsdiscovered by the robot or otherwise recorded by or made known to therobot). If there are too many room identities, the room identities arecombined until the number of rooms equals the number of roomidentities.)

Once the topological map and/or number of rooms are in the robot orsystem, the user map or icon map can be built. The user map andtopological map are distinct. The user map is built using a userinterface presentation at a local or remote client (PC, dedicated, cellphone screen) or on the display of the robot. A person's identificationof room identities and association with markers (or icons) provides theeasiest and most reliable way of unifying the robot's and person's worldviews. The resident or caregiver may or may not be shown the contents ofthe topological map, and connectivity and adjacency from the topologicalmap may or may not be used to display the user map (or be separatelydisplayed superimposed or together with the user map).

As shown in FIG. 21B, in order to build the user map, the robot, basestation, or web application shows possible markers to the user via theinterface in step UM2. As shown in FIG. 22A (depicting a user interfacescreen), one system employs iconography, simple pictures of each roomtype. In the view depicted in FIG. 22A, Office, Living Room, Kitchen,Bedroom (1 denoting that no bedrooms have yet been selected) andBathroom icons and/or text are shown as room identity markers. Alsoshown is an empty graphical representation of a home (a house outlinewith roof). The interface in this case shows the number of roomsremaining to be identified. At step UM4 (which may come before UM2, andmay not depend on nodes but on other methods of determining roomidentity), the robot is moved to a new node, from which the roomidentity is to be verified. At step UM6, the robot shows the robot'sperspective to the person conducting the construction of the user map.As shown in FIG. 22A, the robot's perspective (from one or more cameras28) may be shown to a remote user via the user interface. When this isperformed locally, the user will confirm the present room that the robotis in, but there is no need to show the robot's perspective.

At step UM8, the robot (or web server, etc.) requests assignment of oneof the room identity markers to the robot perspective or the currentroom (“Please confirm which room the robot is in?” from FIG. 22A). Theresident or other constructing the map then selects a room identitymarker. One way of receiving this information is by accepting aselection (cursor-mouse click, touchscreen) of one of the icons as shownin FIG. 22B—one room is then subtracted from the count of remainingrooms, and text confirmation of the selected room is shown.Additionally, at this time or other time, the routine may confirm whichroom includes a home base (charger, dock, RF access point). At step UM12, the room identity (in FIG. 22B, “kitchen” identity is correlatedwith the kitchen icon room identity marker). In step UM 14, the assignedroom identity (“kitchen”) is assigned to the icon map with the properroom identity marker.

Step UM14 is cumulative in nature, i.e., in order to add each assignedroom identity to the icon map and complete the map, steps UM2-UM12 wouldbe conducted for each iteration of step UM 14, until step UM 16 permitsthe process to conclude. FIG. 22C shows the icon map built up, with allrooms to be identified (five) having been identified. Five room identitymarkers correspond to the five assigned room identities, and fiveunknown rooms have been accounted for. The completed map may be storedas an association of the graphics (markers) with the room identities(type and function of room) and further, optionally, with the rooms(including one or more topological nodes). A confirmation checks if theuser has identified all of the rooms accessible. While FIGS. 22C and 22Dshow room adjacency as lines between room identity markers, there is noneed for the user to see these (at the same time, the markers or iconsare optionally arranged according to adjacency and/or with adjacencylines so as to provide the person operating the robot with an intuitivefeel for travel time from room to room). As noted above, the robot mayreceive a selection of a room identity markers via the user interfacelinked to the displayed room identity markers as a first navigationcommand representative of a remote user's selection of a room identitymarker, may recognize a present room, and may previously, at the sametime, or subsequently drive among rooms of different room identityaccording to the first navigation command until the robot recognizesbeing within a room having a room identity corresponding to the selectedroom identity marker.

Directions via the icon map can provide multi mode semi-autonomousnavigation, with decreasing granularity. First, the user selects a roomusing the room identity marker, and the robot uses the room identityand/or topological information to search for a room with the roomidentity until it is located (if a topological map is used, planning aroute rather than searching). FIG. 19 describes the first mode, usingthe icon map. At step IN-2, the robot receives room identity and/ornavigation commands from a user (in many cases a remove caregiver, butalso from the resident if the resident is confined to part of the home,as well as other exceptions). As shown in FIG. 22D, the operator mayclick or select an icon corresponding to a room. The exemplary interfaceof FIG. 22D also identifies the present location and status of the robot10 (kitchen, charging) with text as well as a superposition on the iconmap. The interface in FIG. 22D offers different options, among them toclick on (or otherwise select) the local scene observed by therobot—i.e., to position the robot (via selection of ground planeposition or landmark) and to click on (or otherwise select) a particularroom to travel to. Confirmation steps are not shown, but may be used.

In step IN-4, the robot may recognizes the present room. A variety oftechniques are available as discussed herein, including localization viaRF, fiducials, odometry, dead reckoning, object, pattern, surface, orfeature recognition, and the like. If the room sought is not the one therobot is in (which can be a choice prevented by the interface), then therobot will begin to search for the room at step IN-6. The robot mayfollow a topological map, or may wall-follow, or may use SLAM or othernavigation to begin this search. The search may also be essentiallyrandom. Once in a new room, the robot may stop at a predefined node,pose or arbitrarily, in a position that permits or facilitates roomrecognition. However, it is necessary that the robot identify the soughtroom when found—that a room the robot eventually finds corresponds tothe sought room identity. Methods of recognizing a room are alsodiscussed herein, and if the robot cannot confirm that it is in thecorrect room at step IN-8, the robot moves on to another room. FIG. 19is simplified in that it does not specify a failure mode should therobot never locate the room sought, in most cases this would requireintervention. At step IN-10, the robot will change mode to “webdrive”,permitting the remote or local user to select a position on the groundin the camera view, or a landmark, for the robot to approachautonomously.

Webdrive mode has two sub-modes. As shown in FIG. 22E, a user interfacemay permit the operator to click a feature observed via the robot'steleconferencing camera 28 or navigation camera 29 within the room. Theuser may indicate a desire to “steer” the robot (in FIG. 22E by clickingon or selecting an icon representing the rear of the robot's profile),i.e., use joystick command streaming to directly drive the robot, or to“position” the robot (in FIG. 22E by clicking on or selecting a point orlandmark within the scene), i.e., use an interpreted x-y ground planeposition in the scene as a target for the robot to move to relativelyautonomously, or to “travel,” (in FIG. 22E by clicking on or selecting aminiaturized representation of the icon map) i.e., to return to icon mapmode and select a new room. To web drive, as shown in FIG. 20, the robotreceives a floor location and/or landmark item (which may be convertedto a floor location or node) from the remote use at step WN-2. At stepWN-4, the robot recognizes a present location. The resolution of thepresent location may be rough, i.e., there may be no more than a fewdiscrete recognizable positions in the room. Alternatively, there is noneed for the robot to recognize a present position—instead, it merelyestimates an amount of forward movement using parallax or triangulationfrom the selection made within the scene by the user, and attempts tomove to that position, relying upon behavioral object detection andavoidance to stop short of any hazards which may prevent completing themovement. In either case, the robot begins moving toward the location atstep WN-6, and stops moving when it interprets its position to be thelocation desired, i.e., location reached at step WN-8.

From a new position, although FIG. 20 shows a continuous process anddirect move from web drive by ground plane pointing into a commandstream mode, the operator (remote or local caregiver or resident orother user) may be presented with an opportunity to step up to the iconmap mode or down to the command stream mode, as depicted in FIG. 22E.Once the command stream mode is selected, an exemplary user interfacecould take the form shown in FIG. 22F. The command stream mode takesjoystick-like (trackball, multi-degree puck controller, mouse) movementcommands from the operator and directly moves the robot at a directionand heading according to the command stream. Modifications to directmovement can include behavioral oversight via intervening objectdetection and avoidance, slowing down for persons or objects,spline-curve or other movement prediction, estimation and smoothing, andother provisions to handle latency between command, execution, andfeedback. If ping times are very high, this mode may be disabled infavor of ground plane point web-drive mode.

As shown in FIG. 22F, the command stream mode may use on-screen activearrow controls to simulate a joystick, and may offer a choice ofsteering using these arrows or positioning (by returning to the viewshown in FIG. 22E. As shown in FIG. 22E, in order to steer effectively,it is often useful to have a portion of the robot's body or leading edgeappear in the scene as point of reference for scale, orientation, andsteering. Estimation of gaps, angles, and distances by a human operatoris improved. In FIG. 22E, two different camera views are shown: a groundplane camera which is used for steering clear of objects on the ground,and a robot perspective camera for showing the “eye-level” view from therobot's primary or teleconferencing camera(s) 28. The robot body,steering reference, ground plane view may be from a separate camera orthe same camera. Upon the change to command stream mode at step WN-10,the robot receives a command stream of joystick or controller commandsas discussed above in repeatedly cycling through steps WN-12 and WN-14,and the robot is substantially directly (albeit with latency) movedaccording to the command stream WN-14. An exit signal permits the userto return to other functions of the robot at WN-16.

This navigation ability may also be remotely available to a resident whois away from home, or who may be confined to a particular area of thehome. In such a case, the resident may remotely access the robotinterface, via an internet connection (or via a personal digitaldevice), and select a room or thing on which the resident desires statusinformation. For example, the resident may want to robot to confirm thatthe front door is locked, and selects the living room on the mapdisplayed on his or her web browser. The robot first identifies itspresent location (for example, the bedroom D). The robot then moves fromthe bedroom D, through the hallway F, until it reaches the living roomB, where the front door is located. The robot may then take a visualimage of the front door, and send that visual data to the remoteresident, at which time the resident may instruct the robot to return toit's starting point, or to move to a different location. Alternatively,the resident may first select the room where it wants the robot tonavigate to, then direct the robot to an item or more specific locationwithin that room, then direct the robot to move on to a differentlocation. The robot may also send streaming video to the resident as itmoves throughout the home. Additionally, this mapping and trackingfunctionality may be available to a remote caregiver, with theappropriate permissions, as described herein.

In the course of interacting with a human resident, the robot andresident may become separated within an environment. Should the robotrequire contact with the resident, due to the beginning of a complianceroutine, initiating a teleconference, or otherwise interacting, therobot will be able to navigate the environment to locate the resident. Aplan view of one such navigation path in an environment 400 is depictedin FIG. 14A. The environment 400 may include a number of rooms, such asrooms 1, 2, 3 and 4, as shown, as well as a corridor 402 whichinterconnects each of the rooms. Entry and egress to each of the roomsmay be provided by doors 404, which may be open or closed. The mobilerobot 10 may perform a locating behavior for seeking out the residentbefore beginning an interaction or other robotic behavior that requiresthe presence of the resident. For example, if the robot 10 is docked ata base or charging station 406 when its schedule determines that aregimen must be initiated, the robot 10 may proceed from room to roomwithin the environment 400 while monitoring the robot's immediateenvironment for indications that the resident is present.

In each room, the robot 10 may employ a sensor suite that is responsiveto the presence of a person (including sound detection, movementdetection, pulse, breathing and/or heat detection) and/or an audible orvisual query. The robot 10 also may move to a central area of therobot's known environment 400, or may move to an observation area in itspresent location (a central point in the room, for example), to beginits query. This first initial centralized locating function may behelpful if the robot recently had contact with the resident in the roomor area in which it is still presently located but did not detect theresident leaving the room. The robot may also make a first round ofknown rooms, stopping in positions permitting surveying of large areasand monitor sensors for any responses. Filtering can be used to excludefalse positives (the stove is too hot to be the resident, the dog is toolow to be the resident, etc.).

In an alternative embodiment, the robot may utilize a paging system,with or without the use of sensors, to locate a person. This type ofsystem may also be utilized if the robot is experiencing a sensor orother failure condition. When paging a person, the robot may use thedoorways to separate rooms or chambers, in order to page the residentover only a short (in one embodiment, less than about 5 m) distance,from locations in which a direct line from robot to resident is morelikely. The robot may also use this paging in subparts (smaller areas)of rooms or from passage outside of or between rooms. The robot may pagefrom the doorways themselves in order to reach two rooms with one page.

When a person is detected, the robot may attempt to identify the personby employing an audible or visible query that asks whether the person ispresent, via a speaker and/or recorded speech or sounds, or synthesizedspeech or sounds. If the robot proceeds through every room, as depictedin FIG. 14A, without locating a sound, movement, or heat sourceindicative of a person, the robot may perform a second round of thecircuit or other path through the rooms (starting in the present room),but on this occasion using an audible or visible query in each room.This search strategy may also be utilized if a sensor failure ispreventing the robot from properly operating. Where other means indicatethe presence of the person in the house (e.g., if the robot detects thepresence of a resident's personal radio frequency identification (RFID)tag but no other signs are detected), or confirm the presence of theperson but lack of responsiveness to queries (e.g., pulse and breathingdetected but no response to queries), the robot can conduct proceduresto resolve the inconsistency. These procedures may include requesting acaregiver checkup call, or the robot may place a telephone call into theenvironment searched to make the same queries via phone, or the robotmay contact emergency services.

The mobile robot may also use a secondary system for confirming theidentity of a person, such as by analyzing an infrared image orsignature heat pattern corresponding to the person being sought,performing acoustic analysis to recognize the voice of the person,detecting an RFID or magnetic tag associated with the person or carriedby the person, detecting a particular motion or a gesture, and/orperforming image analysis on a video stream or still image framegenerated by a camera to recognize facial features or memorized clothingsets typically worn by a person.

In selecting a next location to continue a search, the mobile robot mayuse any suitable method, including, but not limited to one or more ofoptical room feature recognition, sonar, RFID room tagging, infrared(IR) directional beacon detection, odometry, inertial guidance, deadreckoning, room mapping, and/or compass navigation. In one embodiment,the robot may use an available heading to a doorway or other wall gap(the heading made available by mapping, by passive detection of beaconsfrom which the heading to a doorway can be inferred, or by active sensordetection of the doorway itself). The mobile robot may also choose anarbitrary path intended to locate a door in a reasonable time (e.g.,wall following utilizing signal reflection) and then proceed until adoorway is detected as having been traversed. The robot may alsoidentify a doorway by analyzing odometry and heading while in wallfollowing mode. Identifying successive odometry/heading combinations mayindicate that a doorway has been traversed. If the mobile robotencounters any obstacles when traveling to the next location, the mobilerobot may circumnavigate the obstacle, or otherwise adjust its path oftravel, in order to proceed to the coordinate location of the selectednext location, or, alternatively, the mobile robot may simply halt atthe obstacle and begin the query process anew. In the case of the robotadjusting its path of travel, once the robot passes an obstacle andencounters its previous heading, it may continue on until apredetermined distance is reached. In addition, the robot may simplymove a threshold distance, ending in either another room, or in the sameroom, before beginning its query.

In addition, as illustrated in FIG. 14A, as the mobile robot encounterswalls and/or doors 404 (either open or closed), it may generate aobstacle, geometric, preference, topological, grid, Voronoi, or othermap of the environment 400. Instead of generating its own map, the mapmay be transmitted to the robot by the resident, possibly as part of astart up, or ownership-initiation sequence. In such a case, the robotmay supplement the transmitted map by identifying locations of transientelements within the environment. Furthermore, the mobile robot may havea upward-facing camera for recognizing pose and/or rooms within theenvironment 400 based on ceiling characteristics (e.g., ceiling edges orconfigurations, patterns of indicia located on or projected onto theceiling, etc.). Such systems are disclosed in U.S. patent applicationSer. No. 11/176,048, the disclosure of which is hereby incorporated byreference herein in its entirety. The mobile robot may also adjust itsmethod of selecting the next location by selecting a next location ornode that is available through a known door or node-connectingtopological branch. On some occasions, potential paths could be blockedby a closed door.

When the mobile robot encounters a closed door, it may attempt tocommunicate with a person on the other side by applying an audiblesignal to the closed door. For example, the mobile robot may include adoor knocker (such as a solenoid) or a speaker which can be applied tothe closed door to transmit an audible signal or announcement to theclosed door. Accordingly, the mobile robot can attempt to contact aperson even when the person may be located in an area that isinaccessible to the robot.

Also, the mobile robot may plan a path to the selected next locationbased on its active or passive detections or map of the environment 400,or it may employ odometry, and/or inertial guidance when navigating. Inthis way, the mobile robot may identify when a door has been traversed,for example. Alternatively, the mobile robot may employ any suitablemethod for navigation, mapping, and room identification, such as, forexample, infrared beam-detection (e.g., the navigation and beaconsystems as disclosed in U.S. Provisional Patent Application Ser. No.60/741,442, RFID room or door tagging, inductive or resonance detectionof tank circuit or amorphous metal tags, optical feature detection orimage analysis. The robot may also utilize Simultaneous Localization andMapping (SLAM), using machine vision-based methods, computationalresources, and sensors, to prepare vision and odometry data of anenvironment. Such systems are disclosed in U.S. Provisional PatentApplication Ser. No. 60/822,636, the disclosure of which is herebyincorporated by reference herein in its entirety.

A locating routine depicted in FIG. 14B may first include checking thelocal area for a resident at (optional) step SL0 (e.g., by pyrolyticheat sensor; and/or sound; and/or visual recognition of movement orclothing; and/or tags or other emitters worn by the resident; and/or anyone of these used to confirm or in combination with at least one other).If the resident is sensed with high confidence, the routine may proceeddirectly to a success routine. However, the routine may also seek toconfirm its detection. Whether the locating routine checks first for aresident or proceeds directly to querying, in step SL1 confirmation ordirect querying may require a simple query in a location where a personis detected or that has not yet been checked: “Are you there?,” asdepicted in SL1. As alternatives, the query may specify the name of theperson being sought, or may be a message intended to imply a lower levelof cognitive ability, e.g., a simple trill or other emotive sound, or a“Mary here?” The mobile robot may then begin a countdown of a timer atstep SL2, and monitor an audio sensor SL3 (such as a microphone) for anyverbal response to the query. If the mobile robot determines that averbal response has been detected at step SL4, the mobile robot may thenproceed to it's next task. On the other hand, if no response isdetected, or if a non-noise response does not correspond to responses inthe robot's library (e.g., “Go away” from a person other than theresident), the mobile robot may check the timer at step SL7. If time hasrun out (as determined at step SL7), the mobile robot may then move to anext location SL8 and repeat the process. Otherwise, the mobile robotmay return to step SL3 and continue to monitor the audio sensor for aresponse until the timer completes its cycle.

The robot's verbal annunciation need not sound like “shouting” orinclude blasting a claxon or other loud sound. Instead, the annunciatorsound levels may be generally inoffensive to others in a room oradjacent room. As an example, normal background noise is about 35 dB,and the annunciator would sound in a normal speaking voice volume ofabout 55 dB to about 65 dB, or at least about 15 dB greater thandetected background noise. If the resident has been identified ashard-of-hearing, the robot may increase the volume to up to about 75 dBor some other threshold level, and may add a visible signal and/oractivate a resident-carried remote vibrator. The annunciator volume maybe reduced to about 10 dB to about 20 dB greater than detectedbackground noise; and/or may be pitched in frequencies that aretypically still audible even to the elderly or those will various typesof hearing loss (i.e., within a range of about 500 Hz to about 5000 Hz).

To facilitate a more rapid response to needs of the resident, or tolimit the amount of time the robot spends away from the resident (thusencouraging more bonding), the robot may be provided with a sensor suiteand reactive behaviors that tend to keep the robot in the vicinity ofthe resident, or track the resident from room-to-room. Simply followingthe resident from room to room may produce annoyance on the part of theresident to the constant presence of the robot; therefore, the robotinstead undertakes actions and tasks that tend to keep the robot near tothe resident, but without close following. The behaviors may (i)increase the probability that the robot is near to the resident, (ii)increase the probability that the robot is in a room or near to a roomwhere the resident has been or will be, and/or (iii) increase theprobability that the time to find the resident will be shorter.

For this purpose, in one embodiment, the robot may maintain a comfort orpresence score (or anxiety score if the implementation is viewed fromanother perspective), which may increase, increment, or fully replenishin the resident's presence and may decrement, decay, or be reduced injumps or steps as time passes or events occur without observing theresident. Once the comfort score decays beyond a threshold value orenters a certain range or region, the robot may register the score as adiscomfort, which may activate or change the priority of aresident-seeking behavior or other behavior that tends to improve theproximity of the robot to the resident. Upon direct querying, sensingthe resident, or checking phenomena that tend to correlate with thepresence of the resident (heat, sound, movement), the comfort score maybe replenished, or be gradually incremented, depending upon thecharacter of the detection of the resident or phenomena.

An exemplary tracking routine that utilizes a comfort or presence score(as that score relates to proximity to the resident) is shown in FIG.15. In a preferred embodiment, improving and decaying such a score areseparate processes, and may occur for separate reasons, although thesame score is affected. Other factors, such as battery condition orcharging dock proximity, may also affect the score. Initially, at stepST2A, the improvement conditions are set, e.g., the score may be set toa maximum (fully replenished) when the resident is proximate, or may beimproved or incremented by a set amount when the resident is proximate.These may be different for different times of day or for different userpreferences. The presence or comfort score improvement process or threadis then started at step ST3A. At step ST2B, the decay conditions areset, e.g., the score may be set to a half (fully replenished) at thebeginning of the day, or may be improved or incremented by a set amount,at a constant rate or at an accelerating rate, when the resident is notdetected. These may be also different for different times of day or fordifferent user preferences. The presence or comfort score decay processor thread is then started at step ST3B. For example, the robot may beginin a bedroom, in an idle, charging, or sleeping state, yet detecting thepresence of the sleeping resident, and maintaining or re-incrementingthe comfort score at a maximum value. The robot may enter a parked orwaiting state, or may approach the resident, monitoring its sensors ST7.If the robot is not directed to follow a person when the person leaves aroom, it may stay in the room, yet the comfort or presence score willdecay according to the thread controlling it. It should be noted thatthe robot may maintain competing scores, e.g., adding a security scorethat measures whether the robot is close to a charging station. So longas the comfort score is within a threshold value, or together with otherscores, the robot may not activate or change the priority of a findingbehavior. This may result in the robot being parked at a charger or inthe last position at which it stopped searching for the resident. Oncethe threshold is crossed (ST5), the robot begins to try to find theresident, leaving the room to find (ST6) and approach the resident. Ifthere is more than one exit to the room, the robot may have recorded andrecall the exit used by the resident (not shown). At some point, therobot may find the room in which the resident is present. When theresident is found, the comfort score or presence score will improveaccording to the ST3A thread, and step ST7 will again approach and parkthe robot proximate the resident.

The robot would then park itself quietly, or with a simple comment ornoise, in the same room as the resident, in a position that does notblock traffic paths. Corridors and very small rooms such as bathroomsmay be off-limits, and the robot may instead park itself in a nearbyroom. At this point, the cycle begins again as soon as the comfort scorereaches a maximum. If the robot does not find the resident, it may seekthe security of the charging station or other comfort generatingphenomena. In this manner, although the robot does not follow theresident, the distance to the resident may usually not be very far, andthe robot may be often in the same room. The robot may also communicatein order to elicit a response from the resident and/or provokeinteraction. Accordingly, the robot may be perceived as a more naturalentity, may maintain proximity to the resident without uninvitedirritating following behaviors, and enhance the likelihood ofsuccessfully interaction with the person, as well as ensuring that theresident is quickly locatable. By using the tracking behavior, the robotincreases the probability that it will be near to the resident when theresident is to be found or when the robot is called by the resident. Therobot need not be within detection range, only closer to the residentthan it was when it started looking, although parking within a detectionrange may require that the robot search less often. If a chargingstation is nearby, the robot dock and charge. Additionally, the robotmay dock and charge with a nearby charger, even if that charger liesoutside of the detection range, if the robot concludes it requiresadditional power.

Alternatively or in addition, the robot may behave in accordance with avirtual pheromone system, in which a room is assigned the comfort scorerather than one score kept by the robot. When the resident is notobserved in a particular room or location, on the other hand, thecomfort score of that room would decline. Entering a room of frequentuse may increment the comfort score, and the robot may tend to navigateto rooms that tend to increase the comfort score. These properties maybe time dependent—the robot may look first in the TV room at 7 μm, firstin the kitchen at noon, and first in the bedroom after bedtime; thedecay rate may be correlated with times of frequent room changing (earlymorning activity) or stability (evening leisure activities). Thus, therobot may choose to seek out the resident in rooms with higher comfortscores before resorting to searching locations with lower comfortscores, and therefore potentially increase the likelihood and typicalspeed of looking for the person. Alternatively or in addition, the robotmay form a comfort-related spatial occupancy map, landmark map, ortopological map that updates features or cells according to theprobability that the feature or cell is adjacent to or occupied by theresident—in this case, each cell corresponding to a room, corridor, or anearly room-sized area.

Alternatively or in addition, the robot may behave in accordance with aforce, vector or potential field that maps a comfort scores/vectors ontoa motor, drive, or navigation goal space. The comfort scores may bevectors or areas of high comfort potential, which may decay over time.The comfort potential of the resident in the potential field may becompared to with the comfort or security potential of the charger, basestation, or recorded wireless signal strength field to decide thelocation where the robot will park itself in the room with the resident.Such fields can define that the robot should be near to, but not toonear to, the resident, and also in a strong wireless signal strengtharea available in that room.

The mobile robot may improve its rate of successfully maintainingproximity to the resident by tracking and following the resident incertain circumstances: e.g., a fixed or variable percentage of the timethe robot successfully detects that the resident has left the room,and/or during certain times of the day, and/or after certain patterns ofconduct by the resident. For example, if the robot recognizes that theresident is beginning preparations to retire for the evening, the robotmay follow the resident from living room to bedroom. Additionally, or inalternative, the robot may record, interpret, or accept inputsdescribing the resident's daily routine or schedule, and may use theschedule to predict and move to an appropriate room ahead of theresident.

The robot may initially become aware of the resident's presence by anyappropriate method, such as by asking whether the resident is presentand receiving an affirmative response, or by having the robot'sattention directed to the resident via a command or input from theresident or a caregiver, for example. The robot may detect the presenceof the resident using a physical sensor or input from a variety ofsensors, such as infrared sensors, heat sensors, motion sensors, opticalsensors, a microphone or other acoustic sensor, electrical propertysensors (e.g., capacitance) or any other suitable physical sensor.Alternatively, the resident may carry a tag such as an active or passiveRF or RFID tag, tank circuit, sonic emitter, light source, any of whichmay carry a modulated signal, or the like, which the robot may use toidentify and locate the resident. Used in conjunction with an item suchas a medical alert bracelet would make such an item very useful forincreasing the reaction time of the robot to various medical situations.As another example, once the robot has located the resident in order toperform a task (as described in the above-described embodiments), therobot may then continue to keep track of the location of the residentand track the resident as the resident moves about the environment.

While navigating an environment, the robot will encounter variouscandidate objects (objects higher than room temperature, in motion, orgenerating noise), which may or may not be the resident sought. In orderto determine whether a candidate object has a high likelihood of beingthe resident, the robot may associate a particular sensor input profilewith the resident, and compare any objects that come within range of therobot with the resident's sensor profile. For example, if Ann is theresident that is being cared for, then the robot may record Ann'saverage temperature using an IR sensor, Ann's approximate size using acamera and/or image analyzer, the clothing combinations typically wornby Ann in the same manner, pitch of Ann's voice or the sound of Ann'sbreathing using a microphone or acoustic sensor, etc., during the courseof performing tasks with or for Ann. Based on these or other inputs, therobot may generate a sensor profile that is characteristic of Ann.Furthermore, the robot may analyze or distill the characteristic sensorprofile of the resident by employing suitable statistical models orrecognition models, e.g., Bayesian analysis, Hidden Markov Models,techniques dependent upon these two, or other statistical or heuristicroutines for filtering and recognizing.

The robot may also track a number of grouped characteristics of anentity, maintain a persistent record of grouped characteristics labeledas a particular entity, and/or the location of that entity in space(including topological space or other abstract representative space).When the robot compares an observed object to the resident'scharacteristic sensor profile, it may generate a comparison score thatgenerally correlates to the likelihood that the observed object is, infact, the resident. If the comparison score of the observed objectexceeds a threshold score, the robot may track the object in order toremain generally proximal to the resident, or may rank the comparisonscores of two or more of the observed objects to determine which objectis more likely to be the resident, or may track new objects instead ofold objects, or may switch tracking from one object to another when thecomparison yields a difference above threshold. The robot may rely onits likelihood analysis without seeking direct identity confirmationfrom the resident. The robot may try to maintain a particular distanceor distance range from the resident, and may react only after a delay ordistance threshold is crossed.

Within an environment, one or more docks or base stations (such as arecharging dock or resupply dock) may be positioned for the robot torecharge its batteries or obtain supplies. A location of one suchcharging station is depicted in FIG. 14A. Each dock may be plugged intoa power outlet on a wall, and permit the robot to interface with thedock for recharging, where the robot has charging terminals at poweroutlet height and/or at dock terminal height. The dock may employcelestial navigation, the robot using an upwardly-directed camera orsensor to recognize a 1- or 2-dimensional bar code, self-similar symbol,or other resolvable symbol projected onto the ceiling or other readilyvisible surface. The resolvable symbol may include informationresolvable to the type of dock (charging, medication or consumableresupply, etc.) in the room, the typical use of the room (living room,dining room, kitchen, bedroom), the adjoining rooms, the number and/orposition of doorways, and/or information recorded by the dock. Thepresence of a dock and type of a dock in a room may increment or changethe comfort score, security score, etc., of the robot to improve theprobability that the robot maintains a viable battery charge. The robotmay detect the presence of the dock through any other suitable method,such as optical scanning for a symbol on a dock, RFID tag detection whenan RFID tag is positioned on the dock, a pre-loaded map of docklocations, etc.

A regimen compliance assistance routine is detailed in FIG. 16. In stepRC-2, the robot checks a database (locally, remotely) of personalregimen compliance information, such as medication dosage informationthat corresponds to the medication regimen of the resident, as well aspostponement rules. The database includes, e.g., how many pills in adose, when and how the medications are to be take, whether they can bedelayed by a few minutes, an hour, before or after meals, whichmedications are to be taken together with others or not with others.This routine is applicable for health oriented regimens (exercise,therapy, meditation, etc.) and where compatible, the discussion hereinof medical dosage information and “doses” includes activities associatedwith any kind of regimen.

The robot checks the information often enough to anticipate that it willneed to be near the resident at a certain time in the future (e.g.,frequently checking ahead to accommodate changes in schedule, or bysetting ticklers ahead of the event). When an event is upcoming(anticipated or known due to a tickler/reminder) at RC-4, the robotbegins to look for the person/resident. In the case of the proximitymaintaining routines discussed herein, the likelihood that the residentis very near is good. However, even absent the proximity maintainingroutines, the robot need only schedule enough time in advance totraverse the entire household, and in most cases will not need to.Rather than employ proximity events as previously described, the robotmay learn a schedule by recording the rooms the resident is found inevery day and time an event is needed, and in short order will learn themost likely room, the second most likely room, etc., for a time of day.The person finding routine employed at step RC-8 is as described herein,and may include a verification step to check the identity of the person.

When the resident has been located and their identity verified, therobot establishes a position next to the resident. The resident may beotherwise engaged, and so the robot takes up a position that ispreferably unobtrusive (E.g., against a wall, in a nearby charging dock,in a corner of the room, beside the arm of the chair in which a residentsits) and awaits the scheduled event. In the case of a generalizedregimen compliance event, at RC-16 the resident is reminded of theregimen activity they are expected to accommodate. For exercise, therobot may act as coach, may display exercises on screen, may link into alive exercise session, and may synchronize its own motions with thoseexercises to be performed by the resident (along with other appropriatemovement expressions, modulated and controlled as discussed herein tomatch particular scripted events or non-scripted stimuli). For therapy,the robot may display therapies on screen, may guide the resident toparticular equipment (or carry the same), may link into a live orrecorded therapist, and may take the resident's reports of statusinformation (e.g. following exercise or therapy, reporting heart rate,blood pressure, breathing rate, either by having the resident measurethem or by using on-board interactive sensors).

It should be noted that as described herein, the robot contains fullconnectivity and support for power, network access, security, andmobility to health assisting appliances, one example of which is a“Health Buddy” available from Health Hero Network, Inc., Redwood City,Calif., and such as those discussed in U.S. Pat. No. 5,307,263, hereinincorporated by reference in its entirety. A typical device is a 1.25 lbdevice with a small color LCD screen, soft buttons, and medicalinstrument and network interfaces. It includes may include USB ports, anRJ-45 Ethernet network port, and embedded-class memory (64 MB) andprocessing (ARM processor, Linux OS). The devices are typically poweredby 5-24V DC via an AC adapter. The contemplated robot can provide morerobust, longer lasting power (2400-9000 milliamp-hours) for appliance orinstruments, as well as smart control of on-off cycles (turning on theHealth Buddy only as needed); mobility and patient finding for theappliance itself as well as instruments, additional network connectivityto additional instruments, wireless devices, pagers, telecommunications;full-screen, full-support, and live tutorials and instructions; videoconferencing, remote observation, statistical reporting, richer controlsand interfaces. Such appliances may be connected via network interfaceto collect data from to blood glucose meters, peak flow meters, scales,blood pressure monitors, pulse oximeters and the like, and robot mayintercept, split, transfer or otherwise link to the same instruments,and the regimen compliance reminder may hand off to or receivedelegation from a Health Buddy or like device pursuant to independent orlinked schedules, and subsequently route collected data, interfaceevents, communications, and all other digitally transmissibleinformation discussed herein via the appliance's supporting networks orthe robot networks discussed herein. The Health Buddy is a Linux devicehaving a limited subset of the connectivity and user interface elementsof a robot as discussed herein, and all of the Health Buddy processes,software and interfaces, including user interfaces displayable on ascreen and controllable by user interface elements such as a touchscreen or soft buttons, may be directly run by the robot discussedherein. As discussed herein, regimen compliance, scheduling,interaction, reporting and all other compliance and medical reportingdiscussed herein, as supported by resident or patient finding,reminding, household navigation and resident location awareness,medication loading and carrying, privacy and permission administration,and human-robot interaction, expressly includes all uses of appliancessuch as the Health Buddy supported by, carried by, and or linked to themobile robot described herein, and the claims herein expressly considersuch an accessory appliance to be fall within the literal language of a“robot,” “robot system,” or method of operating, navigating, orotherwise controlling a robot or robot system.

If the compliance event is associated with the taking of medications,steps RC-12 and RC-14 are specifically applicable. In the context ofthese claims, “matching” is the task of putting the resident in the sameplace at the same time as their medication, and may involve bringing themedication to the person or guiding the person to the medication. In afailure mode where mobility is not working, matching is replaced by merereminders. In step RC-12, a human perceptible signal (recorded speech,synthesized speech, a displayed picture or displayed text, flashing orblinking lights, pointers, outlines, or highlights) is “sent” to theresident, and shows the resident the location where the medication is tobe found (which may in fact be inches away carried by the robot, or maybe in a room where a medication dispenser that is a networked part ofthe robot system is kept, or may be where medication is normally keptfor that resident, as well as other variations discussed herein).Guiding, as discussed in step RC-14, is the task of showing or leadingthe resident to the location of the medication, and may be showing animage of the medication on the robot, a pointer or indicator drawingattention to a robot-carried dispenser, or actually moving the robottoward the bathroom or other room where a dispenser is located whileexpressing that the resident should accompany the robot by spokenmessages, sounds, or expression motions.

One kind of matching is shown in FIG. 17A. In this routine, a regimensupport object could include a robot-carried dispenser as is shown inFIGS. 3A-3C, which may be carried by the robot or in a location storedby the robot, and could also include medical instruments (blood pressuremonitor, glucose, heart rate, etc.) or therapy instruments carried bythe robot or in locations stored by the robot. The robot sends a humanperceptible signal at step M-2 as noted above, indicating the regimenperformance location, in this case the location of the dispenser on therobot. The appearance of the regimen support object (i.e., a pictorialdepiction of it) as the object is positioned on the robot is shown onthe display (which may also be projected onto a nearby surface) orotherwise. The robot guides the resident at step M-4, by showing ananimation or activating secondary indicia near the regimen supportobject, to the object. A second kind of matching is shown in FIG. 17B.In this routine, the robot sends a human perceptible signal in step M-6as noted above, indicating the regimen performance location, in thiscase a room or other location where the medication is kept or othercompliance activity is performed. The robot guides the resident to thelocation in step M-8.

FIG. 18A shows a routine for conducting a reminder routine and providinga remote caregiver with an opportunity to intervene. This routine cantake place at step RC-16 of FIG. 16. At step RC-16 herein, after anappropriate period and a reminder as performed by any method discussedherein, the robot checks for a non-compliance indication, e.g., arecorded refusal and/or failure of the resident to successfully completea schedule regimen event. The robot may record this via any of theinteraction methods discussed herein. The procedure is terminated for asuccessful completion. At step RC-18, the robot connects to the network(using the security and authentication methods discussed herein) and tothe caregiver via a preferred channel (desktop video chat, cell phone,e-mail). The caregiver is given the opportunity to intervene (in somecases, as controlled by the resident's previous granting or refusal ofpermission to permit regimen compliance intervention by the caregiver)at step RC-20. If the caregiver elects to intervene, the robot receivesa communication of a human-perceptible signal (an e-mail, recordedmessage, live chat or telephone call, text to be spoken by the robot)via an inbound communication channel (e.g., a channel crossing thenetwork(s) to which the robot and caregiver are both connected).

FIG. 18B shows a routine for loading medication into a medicationdispenser that can be controlled or monitored by the robot. Aspreviously discussed, such a dispenser can be simple or complex. Asimple version would be a standard plastic compartmented device that iscarried by the robot, in which case the robot does not monitor thedevice but only interacts with the resident. Additional features of adispenser may include: electro-mechanical opening and closing ofcompartments and presentation of compartments; magazining of multi-daydoses or entire bottles of pills; monitoring of magazines, optionallyconnected to payment systems and/or verification by the resident, so asto schedule mail-order or other deliveries of replacement suppliescarrying of “Dixie” cups of pills or water, fillable or disposablebladders of water, or a water bottle; sensored detection of medicationpresence or absence; sensored detection of compartments individually orof a presence or absence of an entire dispenser caddy; any of the aboveconnected to robot or robot base station via simple microprocessortogether with serial interface, sensor bus, general purpose I/O or wiredor RF network.

FIG. 18B describes a routine in which the resident—the person who is totake the medication—loads the dispenser him or herself. As earliernoted, the dispenser may be permanent on the robot, carried by therobot, networked but located in a bathroom or the like, and may alsoswitch between these latter two roles. The steps are mechanistic andsomewhat verifiable, but can be sped through once the resident becomesadept at interacting with the robot and dispenser. Most residents thatcould gain substantial benefit from a robot assistant would beresponsible for their own medication planning in any case. However, inall cases in FIG. 18B, the resident may be replaced with the caregiver,with an orderly, another family member, etc. In step ML-2, the robotretrieves from local or remote memory or database the medicationcomplement for that day, and may also retrieve from local or remotedatabase images of medications in the complement, dosage rules (so as todetermine whether to collect, load, or later supply water when adispenser includes such capability), and the like.

In step ML-4, the resident is asked whether or not he or she is ready toload the dispenser. This is optionally handled as any other complianceevent discussed herein, and can be subject to snooze delays, reportingto the caregiver, and like procedures detailed herein. A simple dialogueis shown at MSG-4 in which the robot checks whether the resident hasleft-over medication in the dispenser, and/or expects that he or she hasall medication available. In step ML-6, the robot repeats and stepsthrough each medication. A simple dialogue is shown at MSG-6, in whichthe robot explains the particular regimen for a medication, uses thename of the medication, shows an image of the medication, and requeststhe user to load a chamber, compartment, disposable cup, or other holderwith the medication. More medications are stepped through in the sameway. The routine does not show more significant interaction (e.g., suchas the resident wishing to ask about side effects or other queries), butmore responsive dialogues (such as are discussed herein) would permitthis to occur. Once the medications have all been loaded, the robot mayask the resident to quickly step through and double-check the day'scomplement (ML-8). If the caregiver is permitted to or designated tocheck the medication complement (ML-10), the robot may open acommunication channel to the caregiver (step ML-10, the same as orsimilar to the above discussion of steps RC-18 and step RC-20), and thenpermit the caregiver to ask questions of the resident (or for a richlyinstrumented dispenser, directly check the status). The dispenser may bearranged (with a transparent or open cover) and positioned so that it isvisible to a camera of the robot, and indeed the resident may hold adispenser so configured up to one of the robot's cameras.

In addition to the above-identified functionality, the robot may beequipped with RFID or barcode sensors for assisting with shopping, etc.In an example, the robot may accompany the resident to a store orsupermarket, in which the items for sale include RFID tags (or barcodes,or any other suitable identification scheme) for identification andinventory. If the resident wants to purchase an item, the robot may scanthe RFID information of the indicated product, and relay the informationto the store for purchasing assistance. In addition, the robot may keeptrack of food or supply inventories in the household by scanning RFIDtags or barcodes of items in the refrigerator or pantry. When items runlow, the robot may retrieve additional supplies and restock, forexample. Such functionality is not limited to only food or store items,but may also be applied to any suitable items, such as clothing,automobile parts, etc.

In addition, the robot may assist in keeping the household clean, bymonitoring clutter or by keeping track of cleaning schedules. A clutterlevel can be scored according to, e.g., (i) a number of collisions orproximity detections per unit time or per unit distance traveled (thesecould be separated into wall, furniture, and non-wall detections basedon sensor data); and/or (ii) a number of differently colored ordifferently textured items per unit area detected by cameras viewing theground plane in front of the robot; and/or (iii) a number ofmedium-range obstacles detected per unit time, distance, or area byranging sensors. In this manner, the robot may apply image analysis toviews of the house obtained from an on-board camera, and determine ifthe house has become too messy, or may determine that clutter hasaccrued when the robot too frequently encounters obstacles along pathsthat should be or are historically clear, for example.

The robot may facilitate bill paying by sharing checklists between theresident and a remote caregiver. Accordingly, when a bill payment orother household task is due, the robot may present a checklist of tasksto the resident on its display screen (and may also verbally or audiblyinform the person). If tasks have not been completed, the robot maynotify a caregiver, if concordant with the privacy permissions. Also,the task checklists may be programmed by either the resident or by aremote caregiver, for example. The robot's cameras also may be used tophotograph and/or OCR bills and notices.

If the resident requires assistance dealing with an outside third partyor service provider, such as a housing contractor, salesperson, or nurseor aide, the robot may provide on-the-spot teleconferencing between thepeople present at the house and the remote caregiver, for example.Furthermore, by providing remote visual inspection capabilities, therobot may facilitate housing safety inspections by permitting a remoteinspector (or caregiver) to view various locations of the house. Therobot may also include safety sensors such as a smoke detector, radongas detector, carbon monoxide or CO₂ sensor, or the like.

The robot may use an infrared emitter to control one or more homeentertainment devices, such as televisions, VCRs, DVD players, or stereosystems. For example, the robot may function as a device coordinator,and control several pieces of equipment simultaneously or according to asequence, such that the robot could turn on both the television and DVDplayer (and switch a stereo mixer to input from the DVD player, forexample) when the resident wants to view a DVD. As another feature, therobot may be easier to locate than a small remote control, and the robotmay also include a database of remote control codes for various productsand manufacturers, relieving the resident of having to program a remotecontrol for multiple items.

Furthermore, the robot (or other appliance having a camera and IRmodulated emitter) may detect RFID, barcode, or brand trademarks on thehome equipment, and discern the appropriate remote control codestherefore without requiring further input from the person. The robot (orremote control or other appliance, having a connection to a camera andIR modulated emitter) may photograph part of or the entire front facepanel of any remote controlled equipment (TV, stereo, video recorder,cable box, CD/DVD/disc player, home theater, amplifier, tuner, lighting,fans, air conditioners, video games, etc.). The robot may then relay animage of the equipment to a remote computer, which may analyze the imagefor brand information or model information, and relay the appropriateremote control code back to the robot, for example, and therefore therobot need not necessarily include image processing capabilitieslocally.

Visual pattern recognition (which may employ a scale invariant featuretransform “SIFT” system such as the ViPR™ system, Evolution Robotics ofPasadena, Calif., or other known scale invariant feature transformalgorithms such as “SURF”) may identify features or distinct regions andcompute from 1-1000 descriptors of unique visual patterns, which incombination may be used to uniquely identify the brand and model (ormodel family) of equipment, including OEM variations. Any portion ofthis process can be carried out on the robot or remotely on a server; inmost cases the robot would simply send the image to the server fordecomposition and comparison to the database of trained equipmentimages. A voting or probabilistic routine can employ feature votes tocross-correlate features in trained images to similar features in therecorded image. The votes are tabulated to identify the most likelyidentity for the equipment or different items of equipment. The robotselects or receives the appropriate libraries of remote control IRmodulated codes for use with every device photographed (e.g., all of thecodes for each of the TV, DVD player, and cable box). A singlephotograph or several photographs may be decomposed or analyzed toidentify every piece of equipment in one place, in a room or in theresidence.

The robot can then employ a compatibility routine to control the devicesaccording to the overall task specified by the resident, by coordinatingcompatibility of inputs and outputs (e.g., in response to a command towatch TV, the robot may activate, via the received IR codes: the TV ON,the DVD OFF, the cable box ON, and the TV to the CABLE input; inresponse to a command to watch a DVD, the robot may activate, via thereceived IR codes, the TV ON, the DVD ON, the cable box OFF, and the TVto the S-VIDEO input). In this manner, the robot would operate similarlyto the family of Harmony™ Remote Controls sold by Logitech Inc., ofFremont, Calif., using a similar database of IR codes and products. TheHarmony devices are programmed by the user, suffer from drift when onecontrolled device is no longer synchronized from the others, and employan all-off routine to reset all devices to a default state in order torecover the input/state synchronization. In contrast, the present robotor remote control or other appliance, having a connection to a cameraand IR-modulated emitter may use the camera and aforementioned visualpattern recognition to detect the on, off, or other active (e.g., wronginput selected, volume low) state of any device by status lights, statusindications (a picture on the TV), status messages (on the TV screen ordevice display) or other pattern recognition to avoid using an all-offroutine, instead resynchronizing the devices to one another based on thepresent state of inputs and other functions. The robot or other devicemay also use speech recognition to receive verbal remote controlcommands from the person, for example.

With regard to verbal input and/or output, the mobile robot may includea database of verbal patterns for various events and/or tasks, such thatthe robot may correctly interpret verbal input associated with aparticular task. For example, when the robot is performing amedication-related task, the robot may load medical terminology into itsimmediate speech-recognition pattern memory; if the robot later performsa shopping task, the robot may switch to a clothing- or grocery-relatedspeech pattern database.

Many examples are given herein that relate to elder care. However, thesame embodiments of the invention are readily adaptable for care ofchildren or in limited cases, adults who require caregiver assistance.In order to provide mental stimulation to the person, the robot may usesound, music, and/or games, either spontaneously, or in response to arequest by the resident or caregiver, or in accordance with apredetermined schedule. In addition, the robot may perform any of thefollowing interactive activities: play games using a touch screen; playword games (audio only, or via the display screen, or both); play music;play audio books; tell stories or recite audio books; play daily newsstories, weather, or sports scores; look up reference information(encyclopedia, TV guides) (in response to verbal input or questions fromthe person, for example); look up financial information (stock prices,bank balance); receive emails and instant messages; show digital photossent by family and friends; play videos sent by family and friends; talkon the phone; participate in a video conference; produce a daily reportsent to a caregiver in email that lists activities the residentperformed that day; play audio clips of the resident talking to therobot; show photos of the resident in their home; give medicationreminders including dosage and timing; give physical activity reminders(e.g., go for a walk, do stretches); give daily event reminders (e.g.,TV show times, appointments, birthdays); let a caregiver talk to and seethe resident from their computer; let a caregiver navigate the robotaround the person's house to check on things; include privacy control(the robot requires permission from the resident before turning on acamera or letting a remote caregiver do a virtual visit; include a tripdetector (the robot detects when the resident is nearby, and gets out ofthe way or makes sounds and flashes lights); include caregivermanagement; and/or give updates (new games, music, videos and photos maybe sent to the robot automatically via an Internet feed, or specificallyby a caregiver or third party from a remote location (via e-mail or webinterface)).

The invention has been described in detail in connection with variousembodiments. These embodiments, however, are merely for example only andthe invention is not limited thereto. It will be appreciated by thoseskilled in the art that other variations and modifications can be easilymade within the scope of the invention as defined by the appendedclaims.

What is claimed is:
 1. A robot system, comprising: a base station; andan autonomous mobile robot; wherein the base station comprises: awireless transceiver configured to communicate transmissions with eachof a plurality of autonomous mobile robots; and an access point circuitfor transferring transmissions between the Internet and the wirelesstransceiver, the access point circuit configured to authenticate each ofthe robots using stored base station security information andcorresponding stored robot security information for each of theautonomous mobile robots; wherein the robot comprises: a drive connectedto a processor to autonomously navigate the robot about an environment;a wireless transceiver configured to communicate transmissions with thebase station; and a client circuit for transferring transmissions fromthe robot to the base station, the client circuit linked to the basestation by stored robot security information corresponding to the storedbase station security information, the client circuit configured sothat, upon activation, the client circuit can authenticate to the basestation using the stored robot security information.
 2. The robot systemof claim 1, wherein the base station further comprises a wired connectorfor accessing the Internet, wherein the wired connector of the basestation is configured to connect to a modem or network terminalconnected to an Internet Service Provider to access the Internet.
 3. Therobot system of claim 1, wherein the wireless transceiver of the basestation and the wireless transceiver of the robot are configured tocommunicate using the 802.11 protocol.
 4. The robot system of claim 1,wherein the base station is configured to authenticate the robot and oneor more other authorized devices on a media access control (MAC)connection-permitted whitelist, and wherein the robot has a MAC addresson the MAC connection-permitted whitelist.
 5. The robot system of claim1, wherein the stored robot security information includes an extendedservice set identifier (ESSID) for the base station.
 6. The robot systemof claim 1, wherein the stored base station security informationcomprises a base station cryptographic key compatible with a robotcryptographic key included in the stored robot security information. 7.The robot system of claim 1, wherein the stored base station securityinformation comprises a private base station key and a public robot key,and wherein the stored robot security information comprises a publicbase station key corresponding to the private base station key and aprivate robot key corresponding to the public robot key.
 8. The robotsystem of claim 1, wherein the stored base station security informationand stored robot security information correspond to a virtual privatenetwork (VPN) or Secure Socket Layer (SSL) connection.
 9. The robotsystem of claim 1, wherein the robot has Wired EquivalentPrivacy/Wifi-protected access (WEP/WPA) enabled by default.
 10. Therobot system of claim 1, wherein the base station is configured toprovide routing functionality.
 11. The robot system of claim 1, whereinthe robot comprises an additional transceiver and is configured to actas a repeater to extend a range of the base station.
 12. The robotsystem of claim 1, wherein the stored base station security informationand stored robot security information both include a predetermined IPaddress for the robot, and wherein the access point circuit of the basestation is configured to require authorization for changing thepredetermined IP address.
 13. The robot system of claim 1, wherein thestored base station security information and stored robot securityinformation both include a predetermined shell level encryption forcommunication between the robot and the base station, and wherein theaccess point circuit of the base station is configured to requireauthorization for changing the predetermined shell level encryption. 14.The robot system of claim 1, wherein the base station has one or morepredetermined ports to the Internet open only to the robot.
 15. Therobot system of claim 1, the access point circuit being configured toauthenticate another robot using the stored base station securityinformation and stored robot security information of the other robot.16. The robot system of claim 1, wherein the access point circuit isoperable as a fleet management tool for the robots.
 17. The robot systemof claim 1, the robot is configured to store the robot securityinformation.
 18. The robot system of claim 1, wherein the base stationand the robot are located within a home in the environment, and at leastone of the robots is configured to assist in cleaning the home.
 19. Therobot system of claim 1, wherein the processor is configured toautonomously navigate the robot about the environment in accordance todata received from an obstacle detection sensor while generating a mapof the environment.
 20. The robot system of claim 1, wherein thewireless transceiver of the base station is configured to receivetransmissions from a remote terminal, and the wireless receiver of themobile robot is operable to receive, from the base station,transmissions including a transmission representing a command generatedby the remote terminal.